Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69748 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77511 invoked from network); 22 Oct 2013 09:52:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2013 09:52:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=bobwei9@hotmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bobwei9@hotmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.86 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.86 blu0-omc2-s11.blu0.hotmail.com Windows 2000 SP4, XP SP1 Received: from [65.55.111.86] ([65.55.111.86:57308] helo=blu0-omc2-s11.blu0.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/9B-10840-2CA46625 for ; Tue, 22 Oct 2013 05:52:02 -0400 Received: from BLU0-SMTP273 ([65.55.111.73]) by blu0-omc2-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Oct 2013 02:51:59 -0700 X-TMN: [mO7WnCH4Fp6PBQlHVRyar34s2KqrAGe7] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Received: from [10.5.4.43] ([158.64.22.1]) by BLU0-SMTP273.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Oct 2013 02:51:55 -0700 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) In-Reply-To: Date: Tue, 22 Oct 2013 11:52:45 +0200 CC: List PHP Mailing Developers Content-Transfer-Encoding: quoted-printable References: To: Pierre Joye , Rethans Derick X-Mailer: Apple Mail (2.1508) X-OriginalArrivalTime: 22 Oct 2013 09:51:56.0016 (UTC) FILETIME=[57D07700:01CECF0C] Subject: Re: [PHP-DEV] [RFC] [Vote] Keywords as identifiers From: bobwei9@hotmail.com (Bob Weinand) Am 22.10.2013 um 11:30 schrieb Pierre Joye : > On Tue, Oct 22, 2013 at 11:11 AM, Derick Rethans = wrote: >> On Mon, 21 Oct 2013, Bob Weinand wrote: >>> I have started the vote for extended keyword support RFC: >>>=20 >>> https://wiki.php.net/rfc/keywords_as_identifiers >>=20 >> 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. >=20 > 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 :) >=20 >=20 > --=20 > Pierre >=20 > @pierrejoye | http://www.libgd.org Thank you for the feedback, I actually don't think that it would be hard to maintain as it still is = only a limited set of keywords where extra conditions are necessary. You rarely should have to change the implementation. If anyone has an idea how I could just write in the parser: "T_STRING or (alphabetic keyword with lowest precedence)" then that'd be very welcome, but I didn't actually find a solution for = that without a lot of reduce/reduce conflicts. See also that initial implementation which just involved parser, but had more limited keyword support: = https://github.com/bwoebi/php-src/commit/18c78af2d9ff27cf2df3ad0e63f5c4cce= 11a5db3 Bob Weinand=