Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89391
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <E3.FB.57156.853A4565@pb1.pair.com>
To: internals@lists.php.net
References: <56547DFE.3080407@php.net> <C8.C9.57156.EB494565@pb1.pair.com>
 <565496FA.2010604@gmail.com> <84.DA.57156.C6B94565@pb1.pair.com>
 <56549E24.7030902@gmail.com>
Date: Tue, 24 Nov 2015 17:50:13 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0)
 Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
MIME-Version: 1.0
In-Reply-To: <56549E24.7030902@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Scalar Type Declaration Syntax Weirdness
From: ajf@ajf.me (Andrea Faulds)

Hi Stas,

Stanislav Malyshev wrote:
> Hi!
>
>> It can't wait for 7.0.1, because banning this would be a
>> backwards-compatibility break with 7.0.0. We have to fix it in 7.0.0 or
>> not fix it ever.
>
> In theory, yes. In practice, if somebody starts using 7.0.0 and
> immediately jumps to using \int, I don't feel too bad for breaking that
> code. We can put a note in release notes for this is needed. But the
> risk of changing syntax parts on the brink of GA IMHO is much larger
> than the risk of somebody using \int in 7.0.0 and getting breakage in
> 7.0.1. Especially if it's clearly described as a bug we intend to fix.

There's no syntax change. We'd be adding another fatal error to 
zend_compile.c triggered by a flag on the token. No messing around with 
the parser.

I understand your concern about the risk, but it's the kind of change 
that wouldn't break anything without it being tremendously obvious.

Thanks.

-- 
Andrea Faulds
http://ajf.me/