Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42095
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: PHP internals <internals@lists.php.net>
Message-ID: <788A2975-EA0F-4493-87D4-3419FBDE79C5@pooteeweet.org>
To: David Grudl <david@grudl.com>
In-Reply-To: <4935A7AF.7010405@grudl.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 2 Dec 2008 23:12:06 +0100
References: <4935A7AF.7010405@grudl.com>
Subject: Re: [PHP-DEV] New namespace implementation
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 02.12.2008, at 22:25, David Grudl wrote:

> 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.


Like Stas said, lets go with what we have and collect some feedback.  
Hopefully we will not have to do any larger changes to namespaces  
after alpha3, but if we have to we will. That being said I really hope  
that people honor the thought process that went into the current  
implementation by really giving things a go without prejudice.

Your comments are noted and not ignored.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org