Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101024 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51696 invoked from network); 1 Nov 2017 23:36:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Nov 2017 23:36:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.169 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.192.169 mail-pf0-f169.google.com Received: from [209.85.192.169] ([209.85.192.169:51879] helo=mail-pf0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id ED/FD-07742-58A5AF95 for ; Wed, 01 Nov 2017 18:36:39 -0500 Received: by mail-pf0-f169.google.com with SMTP id n14so3131427pfh.8 for ; Wed, 01 Nov 2017 16:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YNBUUEY5TMV/9Bauy4NlvMRFAD4avZixn7tAAjgDgoI=; b=BlgMtW+Ch+amFtiL3FJnwSg7CeB3H0XKkJztYmfi5BgasA+pkHkeaEC3dLLxiPfnP3 46TJey1fVpb9pLkbTNOwJBtZnpr/hDwX6CKEnmy7co/9utYr0Be4rx19n7C6yPv8VYZq 8FMum8C1TLjyBt2gbK2aZpkhogVAglo3TbF+4c5dQHXvgT7r6N+LGNgOMOrorHkZyuqb zi7i6/0p31nqMalhC6AqpXaHohKRWGrwDjGuV68t6MpIPKe6ZxVF7W9acxXibhEuNZk9 Q+/g7fktzL9Bldv8sEXNPTujxwrI/nlXl2QyOqP+S0iKodL3cBV+XSVHVrzcWN8VcHlO JWOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YNBUUEY5TMV/9Bauy4NlvMRFAD4avZixn7tAAjgDgoI=; b=OECqeAoO0YX6kfRpaIHUvDoDUUu0+QVERk30Mb8GswDO/ehf2gS2MHqazNz+LRmhLC Eqn+K7qpdS1WCLL+GSPYFiTNh9lbyMZ467skDO90ja/rmeUW4xXsGZo4D3wrfnXXEC19 ZIBDKSAkx8ZZpXsZu+mpsByJfBFqIDb2M1he/a/Kq3SqE5iW4GPhZP3bIe5N/iCeFJI7 FJjuyD9tipXdS5/ZYKi84r/wTOVWAEsSMj2QKJoYnIB/5IMdLlcXluHhoVpFJk/Km/C4 lVhScundy+Ma4+BWs2xlKZ4M6chVD13WMk3BTuteV48/7vSf7ARn9QTtHK1VYzOHRLxJ glwg== X-Gm-Message-State: AMCzsaXJxIoZECUO+8l6gb6Md0BJHHW10fLsRJQonfAGIYyJ/bOQAdYv XAsv4a4mkuxBiYaaDu/mwQr6aowDvdqU6z6Q99M6rD+n+UI= X-Google-Smtp-Source: ABhQp+TNkV9KBQ9JPajEnw3qw9rNUNR/1BoX48m3io5wqC9zaOzrKnfU3SeB4CpQ4HfBZ2HazCDbhC3JU9KIH3Ol0l0= X-Received: by 10.98.223.137 with SMTP id d9mr1546138pfl.98.1509579394403; Wed, 01 Nov 2017 16:36:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.176.11 with HTTP; Wed, 1 Nov 2017 16:36:33 -0700 (PDT) X-Originating-IP: [77.99.17.151] In-Reply-To: <1f9f3be9-532e-533e-ecef-bf567d416941@oracle.com> References: <1f9f3be9-532e-533e-ecef-bf567d416941@oracle.com> Date: Wed, 1 Nov 2017 23:36:33 +0000 Message-ID: To: Christopher Jones , Stanislav Malyshev Cc: "internals@lists.php.net" Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC][VOTE] Flexible Heredoc and Nowdoc Syntaxes From: danack@basereality.com (Dan Ackroyd) Stanislav Malyshev wrote: > > Something I am missing here. RFC is talking about removing indents from > heredoc text, but the vote says "Allow for the closing marker to be > indented?" and does not mention that indenting closing marker also > changes how the rest of the heredoc is parsed. Is this still the case? From the body of the RFC: "To enable for the closing marker to be indented, ... The indentation of the closing marker dictates the amount of whitespace to strip from each line within the heredoc/nowdoc" That's about 3 lines of text into the RFC. Presumably the RFC didn't think the whole concept being voted on needed to be repeated in the voting option. Perhaps it should have been but: Christopher Jones wrote: > I'm going to have to assume so and vote No. It is better to ask questions during the discussion phase of an RFC, but if you do have a question during the voting period, you're still allowed to ask rather than voting based on assumptions. > PS. RFC writers: please take care when writing specs. Please don't use passive aggressive 'helpful hints' like this. For example: "RFC voters - please read the RFC during the RFC period and ask questions then. ;-)" is an irritating way of writing this. A way of writing it that is more conducive to a productive discussion is: I think this is covered in the RFC text. Does the line I picked out above, give a clear description for what that vote is for? cheers Dan Ack