Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92810 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22339 invoked from network); 26 Apr 2016 17:49:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Apr 2016 17:49:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=bjorn.x.larsson@telia.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=bjorn.x.larsson@telia.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.156 cause and error) X-PHP-List-Original-Sender: bjorn.x.larsson@telia.com X-Host-Fingerprint: 81.236.60.156 v-smtpout3.han.skanova.net Received: from [81.236.60.156] ([81.236.60.156:55041] helo=v-smtpout3.han.skanova.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/77-20013-53AAF175 for ; Tue, 26 Apr 2016 13:49:42 -0400 Received: from [192.168.7.7] ([195.198.188.252]) by cmsmtp with SMTP id v77Ba6C6Ry3jdv77Ba0qRY; Tue, 26 Apr 2016 19:49:38 +0200 To: Sara Golemon References: Cc: PHP internals Message-ID: <571FAA37.5070103@telia.com> Date: Tue, 26 Apr 2016 19:49:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfNZ+USi8C8g2m8u+5AKhpZlAaJWLu2H3GF/pxyiuuzqlF0h2l8t9GazMgpbzVOqQ/93aG/79QH07POKAikL0e4hHsnZUa5hKeUsov5wtzcoG01dBnVaF IvmJHzwbyBYHJ+PZpbmcOei/CZu+THYRb5mskXohXUMOCM0dmWPlFJ6VGeVRQ/yjTgnYDe1cJtsGQBXlPb9nkyCx9S8JZkShsCg= Subject: Re: [PHP-DEV] Re: [RFC] [Discussion] Octal overflow detection From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2016-04-19 kl. 01:24, skrev Sara Golemon: > On Tue, Apr 12, 2016 at 7:38 PM, Sara Golemon wrote: >> https://wiki.php.net/rfc/octal.overload-checking >> Because having this expression evaluate to true makes me sad: ("\000" >> === "\400") >> > I haven't heard any responses on this and wanted to bump it back to > the top of your newsreaders. > > For the record, my inclination is to raise a warning on octal > overflow, but not change behavior (at least, not for 7.1, perhaps > later). > > Note that this warning would bubble up during the lexing phase, so an > opcache would prevent it from raising on every page load. That's > probably fine, the alternative is to signal the parser to bake it into > the ast output and that's way over-engineered. > > -Sara > This reminds me a bit about the RFC: https://wiki.php.net/rfc/invalid_strings_in_arithmetic. So an E_WARNING it should be and option 2. In my opinion no deprecation is needed. Cheers //Björn