Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69753
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.76 as permitted sender)
Message-ID: <BLU0-SMTP407E751FAF3923658C89CDBE2020@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
In-Reply-To: <52664B00.3030409@php.net>
Date: Tue, 22 Oct 2013 12:08:42 +0200
CC: List PHP Mailing Developers <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
References: <BLU0-SMTP246429F66DC7B144E131FE7E2010@phx.gbl>	<alpine.DEB.2.10.1310221010490.5542@whisky.home.derickrethans.nl> <CAEZPtU71ZzWpiAHTs+QHH9KxwGCdg0f5LfR3+8qYavkBJJZQ6Q@mail.gmail.com> <52664B00.3030409@php.net>
To: Sebastian Bergmann <sebastian@php.net>
Subject: Re: [PHP-DEV] [RFC] [Vote] Keywords as identifiers
From: bobwei9@hotmail.com (Bob Weinand)

Am 22.10.2013 um 11:53 schrieb Sebastian Bergmann <sebastian@php.net>:
> On 10/22/2013 11:30 AM, Pierre Joye wrote:
>> I did not vote yet, however I agree with Derick. A cleaner solution
>> would be better. We have lived with this restriction for some time
>> already and we may as well delay this RFC until we have a viable
>> technical solution. If anyone feels motivated enough to implement the
>> parser/lexer using other tools :)
> 
> The implementation has to be clean and the experience to users has
> to be consistent. Last time I looked at the RFC the implementation
> only allowed some keywords to be used in some contexts where keywords
> could not be used previously. Not allowing all keywords in all contexts
> only leads to confusion.

I had announced previously on the list and it's noted in the RFC too, that
these inconsistencies had been removed.

That's actually not the problem; Pierre and Derick are talking about the
implementation in C.

Bob Weinand