Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69168 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46031 invoked from network); 17 Sep 2013 15:23:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Sep 2013 15:23:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=igor@wiedler.ch; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=igor@wiedler.ch; sender-id=unknown Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.175 cause and error) X-PHP-List-Original-Sender: igor@wiedler.ch X-Host-Fingerprint: 217.26.49.175 mxout015.mail.hostpoint.ch Received: from [217.26.49.175] ([217.26.49.175:25377] helo=mxout015.mail.hostpoint.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8B/D1-34196-5F378325 for ; Tue, 17 Sep 2013 11:23:35 -0400 Received: from [10.0.2.46] (helo=asmtp013.mail.hostpoint.ch) by mxout015.mail.hostpoint.ch with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VLx7i-0005eO-03; Tue, 17 Sep 2013 17:23:30 +0200 Received: from [84.73.218.139] (helo=[10.0.1.62]) by asmtp013.mail.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VLx7h-000Kvv-UH; Tue, 17 Sep 2013 17:23:29 +0200 X-Authenticated-Sender-Id: igor@wiedler.ch Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) In-Reply-To: Date: Tue, 17 Sep 2013 17:23:12 +0200 Cc: Developers Mailing List PHP Content-Transfer-Encoding: quoted-printable Message-ID: <355C8F7E-6594-4F88-8FB6-EB771753B926@wiedler.ch> References: <20130917142758.GA26444@analysisandsolutions.com> To: Bob Weinand X-Mailer: Apple Mail (2.1510) Subject: Re: [PHP-DEV] Support for keywords where possible From: igor@wiedler.ch (Igor Wiedler) Hi Bob, Thanks for working on this. The amount of reserved keywords in PHP is quite large and I've = experienced many cases where it would have been useful to use them. = Especially when implementing a DSL, parser, code generator (quite common = use case with template engines, and various other tools), this is often = an issue. The engine supports those "reserved" names without issues, and you can = often actually support them by subverting the parser. As such, = supporting them directly makes sense to me. Regards, Igor