Re: T_IMPORT vs. T_USE
| From: | Sebastian Nohn | Date: | Wed, 17 Oct 2007 18:58:24 +0000 |
| Subject: | Re: T_IMPORT vs. T_USE | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-32835@lists.php.net to get a copy of this message | ||
Are there already any results on these checks?
- Sebastian
On 10/2/07, Andi Gutmans <andi@zend.com> wrote:
> Of course not (and I know we use import in a few places in ZF) which is why I want to see
> whether it makes sense to allow reserved words. The basic parsing rule would be easy but we need to
> check how many other areas this might affect. Wouldn't want to introduce any more
> inconsistencies. If it ends up being too much of a bother we can just end up using "use".
>
> Andi
>
> > -----Original Message-----
> > From: Sebastian Nohn [mailto:sebastian@nohn.net]
> > Sent: Monday, October 01, 2007 11:16 PM
> > To: Andi Gutmans
> > Cc: Johannes Schlüter; Sebastian Bergmann; internals@lists.php.net
> > Subject: Re: [PHP-DEV] T_IMPORT vs. T_USE
> >
> > 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.
> >
> > I don't think people will care much about use vs. import
> > perception-wise. But they will care a lot if it breaks their software.
> > Just to name two popular products that will break (Johannes can for
> > sure
> > tell more, he googled for it): Serendipity & Zend Framework. At least
> > breaking the latter should not be "your" preference, I hope.
> >
> > - Sebastian
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
>
>