Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42093
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain grudl.com from 74.125.78.26 cause and error)
Message-ID: <4935A7AF.7010405@grudl.com>
Date: Tue, 02 Dec 2008 22:25:03 +0100
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Subject: New namespace implementation
From: david@grudl.com (David Grudl)

I just read the new namespace documentation and I must say that the new 
implementation is much more flexible.
Great work!

I had only two objections:

1) False warnings

As http://php.net/manual/en/language.namespaces.importing.php says, it 
is possible to import non-compound name.

    // importing a global class
    use ArrayObject;
 
but it generates Warning: The use statement with non-compound name 
'ArrayObject' has no effect.

2) Relative Resolving

I pointed out to inappropriate relative resolving earlier 
(http://news.php.net/php.internals/41837). In the world of well-written 
namespaced frameworks the ratio of usage of "more nested" classes vs. 
"less nested" is in large majority in favor of the second 
(http://news.php.net/php.internals/41980), but PHP prefer the first way. 
Now, the new implementation offers way to resolve names relative when it 
is needed - using 'namespace' operator (as equivalent of the 'self' 
operator). So I think now there is no reason to use default relative 
resolving and it should be removed.

What about voting?

David Grudl