Newsgroups: php.internals,php.internals
Path: news.php.net
Xref: news.php.net php.internals:41967 php.internals:41969
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain grudl.com from 74.125.78.24 cause and error)
Message-ID: <49214AED.7090903@grudl.com>
Date: Mon, 17 Nov 2008 11:43:57 +0100
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
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: [PHP-DEV] Re: Namespace resolution rules has been changed?
From: david@grudl.com (David Grudl)

> true, however i have a counter example: classes from more general namespace 
> that use further nested classes (think some kind of behaviour and different 
> drivers/plugins for example).

> so while it's true that more nested classes usually extend the less nested 
> ones it also common for more generic code to use it's namespace descendants. 
> in sutch condition possibility to use just the remaining namespace part is a 
> big help and i'd say it's usage would be more comon than single "extends" at 
> class definition where you're obligated to supply FQN [1].

The more generic code (i.e. application code) is located usually in its own namespace, so it must use FQN. FQN with leading backslash.

DG.