Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32523
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error)
Message-ID: <47014EE9.9000806@chiaraquartet.net>
Date: Mon, 01 Oct 2007 14:47:53 -0500
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Andi Gutmans <andi@zend.com>
CC: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>, 
 Sebastian Bergmann <sb@sebastian-bergmann.de>,
  internals@lists.php.net
References: <fdohj3$bul$1@sea.gmane.org> <1191237850.2903.19.camel@johannes.nop> <698DE66518E7CA45812BD18E807866CEB9528E@us-ex1.zend.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CEB9528E@us-ex1.zend.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV]  T_IMPORT vs. T_USE
From: greg@chiaraquartet.net (Gregory Beaver)

Andi Gutmans wrote:
> Hi Johannes, Our preference would be to stick to "import" because I
> think the perception many will have of "use" is that it also includes
> files (just based on some other languages). That said I agree that
> compatibility would be an issue here. In fact it's even somewhat of
> an issue with "namespace" which is probably also used quite a bit
> esp. in relation to XML.
> 
> What I'd like to do is see if it's feasible to support reserved words
> as identifiers. It should be possible but we need to see if it makes
> sense, how it affects consistency, and if we do it what identifiers
> we'd do it for (or all?).

This would be pretty easy, in a hackish way, by adding a whole bunch of
duplicate rules T_FUNCTION T_STRING, T_FUNCTION T_IMPORT, T_FUNCTION
T_NAMESPACE and so on.  A more robust way would be to move to lemon/re2c
but I'm not volunteering to do this (yet?)

:)
Greg