Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32533
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain nohn.net designates 85.214.77.40 as permitted sender)
Message-ID: <4701E210.70109@nohn.net>
Date: Tue, 02 Oct 2007 08:15:44 +0200
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
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: sebastian@nohn.net (Sebastian Nohn)

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