Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36820
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain eenterphace.org from 212.227.92.30 cause and error)
Cc: internals@lists.php.net
Message-ID: <92FD0233-98E7-41B0-9202-AFD15BB12F72@eenterphace.org>
To: Greg Beaver <greg@chiaraquartet.net>
In-Reply-To: <47F8C6C2.3080001@chiaraquartet.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sun, 6 Apr 2008 16:51:50 +0200
References: <5D0C3386-C2BC-4086-87BB-806E2350B373@eenterphace.org> <47F8C6C2.3080001@chiaraquartet.net>
Subject: Re: [PHP-DEV] Re: namespace implementation (irritating warning and autoload)
From: jr@eenterphace.org (Julian Reich)

Hi,

> This is a clear bug, please report it at bugs.php.net
Done: http://bugs.php.net/44653

Since "use SomeName" does the same as "use ::SomeName" dropping the  
warning also be an option.

And if we split of "use" into "use namespace" and "use class" we could  
resolve ambiguous calls where
a namespace and a class have the same name in a way easy to  
understand. This would invalidate the
reason for the warning IMO.
Another benefit is that this way we know whether a unqualified call  
should resolve to a static method or a
namespaced function and can save lookups at runtime.
Furthermore if traits were added to PHP we can simply use "use trait  
TraitName". So there is no room
for confusion because of keyword reuse.

I think splitting of "use" was proposed on this list before but was  
never discussed.


Regards,
Julian Reich