Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88659 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65061 invoked from network); 4 Oct 2015 10:17:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Oct 2015 10:17:30 -0000 X-Host-Fingerprint: 109.111.195.162 unknown Received: from [109.111.195.162] ([109.111.195.162:3634] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/75-31315-ABCF0165 for ; Sun, 04 Oct 2015 06:17:30 -0400 Message-ID: <12.75.31315.ABCF0165@pb1.pair.com> To: internals@lists.php.net References: <560EF0FA.9050300@thefsb.org> Date: Sun, 4 Oct 2015 11:17:27 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 SeaMonkey/2.35 MIME-Version: 1.0 In-Reply-To: <560EF0FA.9050300@thefsb.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 109.111.195.162 Subject: Re: [PHP-DEV] Strings, invalid escape sequences and parse errors From: ajf@ajf.me (Andrea Faulds) Hi, Tom Worster wrote: > > I agree with Sara all the way except the opinion that it's too late to > fix this bug with option B, which I think is the right one. > > I simply don't know if it is too late or not so I suggest Peter enter a > bug report and see what happens. If it's too late for 7.0.0 do it in > .0.1, which is ok because people will expect instability with 7.0.0. > \u{394}semver > 1 is sufficient warning, I think. The RFC was passed with 92% voting in favour, and that RFC INCLUDED the error behaviour explicitly. If people really want to butcher it under the guise of "consistency" and cause future pain when the Unicode consortium does something weird, we should have yet another discussion and voting period. We shouldn't just "fix" it quickly because three people on the mailing list think so. Thanks. -- Andrea Faulds http://ajf.me/