Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75850
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.174 as permitted sender)
Message-ID: <53CE6B55.40104@gmail.com>
Date: Tue, 22 Jul 2014 14:47:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c9Fb0dswXcen8tnkQLEWhBymJ-w30z+p=vj3uRzdS3mGQ@mail.gmail.com> <CAF+90c9Cg7cfJ7p4JDVMEUzVKar4vwzpZfQhxmaFE=oi_sibOA@mail.gmail.com> <CAH-PCH6-UOyc6wZg=QcQFoRuZCh7bks1pRRE+bpGPU6NvC9h7A@mail.gmail.com> <8E0F15AF-8C44-4C19-BE64-A939D897BE77@apfelbox.net>
In-Reply-To: <8E0F15AF-8C44-4C19-BE64-A939D897BE77@apfelbox.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Re: [VOTE] Uniform Variable Syntax
From: rowan.collins@gmail.com (Rowan Collins)

Jannik Zschiesche wrote (on 22/07/2014):
> the point Derick was trying to make is that you can’t build a scanner that automatically checks whether you rewrote this particular piece of code already or not.
> You can find the code pieces which match the constructs affected by the BC, but the scanner can’t decide, whether they are already fixed (= they are ok as they stand).

I thought for each ambiguous case whose behaviour would change, there is 
a pair of unambiguous forms (one for each interpretation) which work the 
same under both parsers?

If so, wouldn't it be possible to change every occurrence detected by 
the scanner to the appropriate unambiguous form (even if that is 
technically unnecessary for that particular case); then when you re-ran 
the scanner, it wouldn't find the same ones again?

I'm probably missing a subtlety here, though...
-- 
Rowan Collins
[IMSoP]