Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101025 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63487 invoked from network); 2 Nov 2017 04:24:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Nov 2017 04:24:23 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.41 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 74.125.83.41 mail-pg0-f41.google.com Received: from [74.125.83.41] ([74.125.83.41:43411] helo=mail-pg0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/EE-07742-6FD9AF95 for ; Wed, 01 Nov 2017 23:24:23 -0500 Received: by mail-pg0-f41.google.com with SMTP id s75so4003864pgs.0 for ; Wed, 01 Nov 2017 21:24:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=nJZEkgT7rTqlesnXrPtWZnU/JtydFHn60uypYUyQFCI=; b=LktQRMDy5MiHDCc7KQIx3viEuYEcAW4B/iOXss6yOmO4EiuHkxEQqS+L/AKs1jkezi AiMDF+f1FvwzvGt3aDnnV1ee8yGrnMgJOLt2aI5QzEGY+gByxXft93LI07t/m6pww4YX vC202Un6YxOIkHyGvD682VXYTQzKoWYh/sEx2SbysiMtNh8Zr/1Sxnsb3tRpcG6J8BDn v7+h+HOpGAFZf15EJsNSjpj5BNGdJ4KqmiP2W+IJ3v+3dvHAtfi82TimG4oF/ezurJw1 QNtE5+flo/trcv/AWEKJnYTX+t84UjAJYbGheIdsGGFHoZrSYijzt/X4BdgzwoqJ9Ipz wNng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=nJZEkgT7rTqlesnXrPtWZnU/JtydFHn60uypYUyQFCI=; b=Q5sTDpb1PuOazge1+6m30vCdzJ8eEqfNyD0uKg3KzGmq2PxGzbUvKVtPVb5ds1esPC U6CfWPMvRpH2BCw9AP1PgOws2uO0qhMiI2VC/nh/FA9WetHKmRO1rA18x0uqeLRFbHfZ zJSS+QPzy0mBfYHOIXEslp9xBJ6gmJCcMtNAHawokBauZa6nI7wza/A7d4YrKRgHzLOr wYsDGawAMM5kjdv4LJmMTENTGAwomuh9IEGdx2Lcam8UK/moqtUc2iTCCKUaqi8WIaqI O5ZqEOvODhcfzzeVd5yhItperULiv1hLXOAeQ53i6caAWNgB0PrDCpg110vF0twgYqfL +19w== X-Gm-Message-State: AMCzsaU2PV00jHlAxAmLkjSykDrJpw6HPiBedMDJ3MHr/3gs2novUt+R kgrCCMbA3K+Pi/QPtXpcNd/0ozY= X-Google-Smtp-Source: ABhQp+RH+y5Y1v8ETerPyTPLaYvOvkakvWi8gMF+5aCY/VE/1WUnHAC9v+jfPQI/nV+R7hRfCWIlvw== X-Received: by 10.98.233.21 with SMTP id j21mr2244012pfh.97.1509596659248; Wed, 01 Nov 2017 21:24:19 -0700 (PDT) Received: from Stas-Pro-2016.local (c-73-71-144-171.hsd1.ca.comcast.net. [73.71.144.171]) by smtp.gmail.com with ESMTPSA id y83sm3679022pfa.31.2017.11.01.21.24.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 21:24:18 -0700 (PDT) To: Dan Ackroyd , Christopher Jones Cc: "internals@lists.php.net" References: <1f9f3be9-532e-533e-ecef-bf567d416941@oracle.com> Message-ID: Date: Wed, 1 Nov 2017 21:24:17 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC][VOTE] Flexible Heredoc and Nowdoc Syntaxes From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > 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" Yes, that's what the RFC says. But the voting question only mentions indenting the marker. I'd prefer voting options were clear and I didn't have to second-guess the intent. It could be "Allow indenting the marker and stripping the whitespace?" and all would be clear. > "RFC voters - please read the RFC during the RFC period and ask > questions then. ;-)" is an irritating way of writing this. I've read the RFC, that is exactly why I was asking - because the voting question did not match the text of the RFC, omitting rather serious side effect. -- Stas Malyshev smalyshev@gmail.com