Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75339 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47515 invoked from network); 8 Jul 2014 15:41:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jul 2014 15:41:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=truth@proposaltech.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=truth@proposaltech.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain proposaltech.com designates 74.115.204.51 as permitted sender) X-PHP-List-Original-Sender: truth@proposaltech.com X-Host-Fingerprint: 74.115.204.51 relay-hub201.domainlocalhost.com Received: from [74.115.204.51] ([74.115.204.51:15277] helo=relay-hub201.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/D0-41998-0411CB35 for ; Tue, 08 Jul 2014 11:41:53 -0400 Received: from MBX242.domain.local ([169.254.2.137]) by HUB201.domain.local ([192.168.68.45]) with mapi id 14.03.0174.001; Tue, 8 Jul 2014 11:41:49 -0400 To: PHP internals Thread-Topic: Uniform Variable Syntax Thread-Index: AQHPmsCC+cdV49D/AUetFxmws0xa+w== Date: Tue, 8 Jul 2014 15:41:48 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.64.24] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Uniform Variable Syntax From: truth@proposaltech.com (Todd Ruth) On 8 Jul 2014, at 15:48, Derick Rethans wrote:=0A= > I've just voted "no" for this, because it introduces a tiny BC break.=0A= > Now, I realize this is a tiny BC break, but it is just *those* that=0A= > drive people nuts when upgrading. There is so much non-public code - a=0A= > cursor check of Symfony and ZF is not representative.=0A= =0A= From Andrea Faulds:=0A= > It is a tiny BC break and it=92s for PHP NEXT (i.e 6 or 7), not 5.6. Why = not? It=92s a =0A= > tiny change which will bother some people but make everyone =0A= > else=92s life easier.=0A= =0A= Thank you, Derick, for voting against a BC break.=0A= I do appreciate the intention of making things more consistent.=0A= Given that this is a parser change, I wonder if there is hope of mitigating= the BC issues by providing an option to generate "new" code from "old" cod= e. Today, I can run "php -l" and php will tell me about syntax problems. = If php6 had a "php --convert-from 5.4.30" that would read in a file that wo= rked in 5.4.30 and output a file that does the same thing using php6 syntax= , I think that would be a Good Thing. Perhaps it would be better as a tool= on the side than as part of the main php executable. I know such a conver= sion process is effectively impossible for some BC breaks; I don't know abo= ut this one. This RFC struck me as a better candidate than usual.=0A= =0A= Thanks for your consideration.=0A= =0A= - Todd=