Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.187 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bK4f+LknFzlqvoJpZG2dWPTZTT/1Y3eBzViJfdekcKfzl+qZeqJuw+jOb5dWQT4Kddim/K/UpQXkwPkZ4a6i2m2svymkmqtIeqFTMHG7G9qCuNa9Yf2657OvBdIenS/HSWlecdmXFNHUUJo7n59i6q/jyzGz3k6gOSyOXrGYflU=
Message-ID: <fe05d1540710180539o4a1b07b7kc918112cd60f7eb9@mail.gmail.com>
Date: Thu, 18 Oct 2007 14:39:17 +0200
To: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>
Cc: internals@lists.php.net
In-Reply-To: <1192702902.3026.9.camel@johannes.nop>
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>
	 <8c631e020710171158n25b5efedt4eccf7d816331407@mail.gmail.com>
	 <47166930.7000706@zend.com>
	 <698DE66518E7CA45812BD18E807866CECC6469@us-ex1.zend.net>
	 <fe05d1540710180308m17409206ibade2a7942afe609@mail.gmail.com>
	 <1192702902.3026.9.camel@johannes.nop>
Subject: Re: [PHP-DEV] T_IMPORT vs. T_USE
From: pierre.php@gmail.com (Pierre)

Hi,

On 10/18/07, Johannes Schl=FCter <johannes@php.net> wrote:

> On Thu, 2007-10-18 at 12:08 +0200, Pierre wrote:
> > I would prefer Stan's patch to allow keyword to be used as
> > class/method/function name. At the very least (the patch has
> > unsolvable issues), I have to agree with Andi, we should just go with
> > "use" (codesearch returns less than 10 results :).
>
> The point about using "use" is that "use" is already a reserved keyword
> in PHP - therefore we can't break anything by using "use" for
> namespaces.

Oh, I missed this point. So what are we waiting for to switch? It will
ease our life to test our existing code under 5.3 without having to
create specific branches (or breaking bc).

>So in this single case we have a chance of using a keyword
> withou breaking anything (while we still might break stuff due to the
> "namespace" keyword) :-)

The namespace keyword is less a problem than import. It is mostly used
in areas where php5+ provides native solution (for example xml or soap
like in ezpublish, mostly php4 code).

--Pierre