Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32835
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.225 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=KvCEWihQXsOQNIthEv06JMCJkYMxzvn5QXyVN1c9CSvFSX2KjG3sPY/lq00LnmdVFhTPHqMNF9wyecOt3xnx6A1WNQywkIMVkjjaLEfKmPFMTAyxAGif0NsH4wPMT/e8ujXUUXusaZi3CfLfjJ4OWSj0vb8wI2K8EBk7KVt6T+Q=
Message-ID: <8c631e020710171158n25b5efedt4eccf7d816331407@mail.gmail.com>
Date: Wed, 17 Oct 2007 20:58:24 +0200
Sender: sebastian.nohn@gmail.com
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
In-Reply-To: <698DE66518E7CA45812BD18E807866CEB954E9@us-ex1.zend.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <fdohj3$bul$1@sea.gmane.org>
	 <1191237850.2903.19.camel@johannes.nop>
	 <698DE66518E7CA45812BD18E807866CEB9528E@us-ex1.zend.net>
	 <4701E210.70109@nohn.net>
	 <698DE66518E7CA45812BD18E807866CEB954E9@us-ex1.zend.net>
Subject: Re: [PHP-DEV] T_IMPORT vs. T_USE
From: sebastian@nohn.net ("Sebastian Nohn")

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 w=
hy 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 m=
ight affect. Wouldn't want to introduce any more inconsistencies. If it end=
s 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=FCter; 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
>
>