Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69747
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.10.1310221010490.5542@whisky.home.derickrethans.nl>
References: <BLU0-SMTP246429F66DC7B144E131FE7E2010@phx.gbl>
	<alpine.DEB.2.10.1310221010490.5542@whisky.home.derickrethans.nl>
Date: Tue, 22 Oct 2013 11:30:09 +0200
Message-ID: <CAEZPtU71ZzWpiAHTs+QHH9KxwGCdg0f5LfR3+8qYavkBJJZQ6Q@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Bob Weinand <bobwei9@hotmail.com>, 
	Developers Mailing List PHP <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] [Vote] Keywords as identifiers
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Oct 22, 2013 at 11:11 AM, Derick Rethans <derick@php.net> wrote:
> On Mon, 21 Oct 2013, Bob Weinand wrote:
>
>> I have started the vote for extended keyword support RFC:
>>
>> https://wiki.php.net/rfc/keywords_as_identifiers
>
> Just to explain why I voted "no". I think the idea is good, but what I
> see from the patch is that it adds a *lot* of hand written state
> machines which are going to be a pain to maintain. I do not think this
> extra maintenance is worth the features - we've done pretty well without
> it.

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 :)


-- 
Pierre

@pierrejoye | http://www.libgd.org