Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76977 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71292 invoked from network); 31 Aug 2014 04:39:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Aug 2014 04:39:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=tjerk.meesters@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tjerk.meesters@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.44 as permitted sender) X-PHP-List-Original-Sender: tjerk.meesters@gmail.com X-Host-Fingerprint: 209.85.220.44 mail-pa0-f44.google.com Received: from [209.85.220.44] ([209.85.220.44:34776] helo=mail-pa0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3B/72-50403-EE6A2045 for ; Sun, 31 Aug 2014 00:39:11 -0400 Received: by mail-pa0-f44.google.com with SMTP id rd3so9627760pab.3 for ; Sat, 30 Aug 2014 21:39:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=I2ETwtn7WjhgKtOpGt4RLIlYa6vhqgsY56qiHzpBidU=; b=i0b9ZHrZM8XVQE9GvXdDsqPzfTAhEwIBPnyl7WfXQGBz2rNkX1XPFF6fznKJNsgjSZ KAlbEKuksncM1rg8YdNVr6HQQK7u8XxI6yrEzg5JyhlyJlLE4dDmHIXkc4ZfMtIkJ440 +5LphLbcnT2wp4LMD7SiHcw7k75dYM4g6Vif1sKWXEAG0PetMee6OjRdDtI2md4FLaOo 09cZC2a6dNhmafx8j4JnNRmUqfYtUc9auZwueeVdgaSHKhKdjH377MG9e3u4r8IDH9pv j7oe6CeKbqCQUFiGiC3oSIrer/FaDVhgOK5PhgQv3zRi7OZ7fVqsKk7083LubdVoJt3J K/LQ== X-Received: by 10.68.215.106 with SMTP id oh10mr17143026pbc.98.1409459947651; Sat, 30 Aug 2014 21:39:07 -0700 (PDT) Received: from [192.168.1.102] (bb121-7-198-24.singnet.com.sg. [121.7.198.24]) by mx.google.com with ESMTPSA id dl8sm6364353pdb.65.2014.08.30.21.39.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 30 Aug 2014 21:39:06 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <54024C60.2040001@sugarcrm.com> Date: Sun, 31 Aug 2014 12:39:02 +0800 Cc: PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <54016A45.1010900@sugarcrm.com> <54024C60.2040001@sugarcrm.com> To: Stanislav Malyshev X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [RFC] Loosening heredoc/nowdoc scanner From: tjerk.meesters@gmail.com (Tjerk Meesters) On 31 Aug, 2014, at 6:12 am, Stas Malyshev = wrote: > Hi! >=20 >> There=92s no real objective measure with which I can answer such >> questions :) >>=20 >> The closest I could come to a rebuttal is if there=92s no real need = to >> make the syntax so restrictive, why not make it less restrictive? >=20 > "Why not" is usually not a very good reason for a change in the = language > syntax. There is, however, a reason why it is restrictive - so that > there would be less chance for the end tag to collide with the actual > text being heredoc'ed, and so that the end of the text would be = clearly > demarcated (since the text itself, being taken verbatim, can not be > properly indented/delimited within the text). I agree, but I can see how this argument is going in circles; my point = (and that of Nikita) is that if the enclosure naturally occurs within = the quotation, it=92s a bad enclosure and a better one should be picked. = The rule of requiring a newline directly following the closing delimiter = is more of a hindrance than it is helpful imo. >=20 > My belief is that the change have positive value of "changing = something > for the better minus changing something for the worse" and so far I'm > not really convinced as of now that this change has it, especially = given > the BC break potential. > --=20 > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/