Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32885
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain horde.org designates 66.92.78.250 as permitted sender)
Message-ID: <20071020172832.338919lgcfp4v1us@technest.org>
Date: Sat, 20 Oct 2007 17:28:32 -0400
To: Stanislav Malyshev <stas@zend.com>
Cc: Gregory Beaver <greg@chiaraquartet.net>, internals@lists.php.net
References: <20071019224202.20245u5zry52h5c8@technest.org>
	<47196F1A.80400@chiaraquartet.net> <471A6BC6.3090608@zend.com>
In-Reply-To: <471A6BC6.3090608@zend.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.2-cvs)
Subject: Re: [PHP-DEV] Re: Order of class resolution with namespaces and
	autoload
From: chuck@horde.org (Chuck Hagenbuch)

Quoting Stanislav Malyshev <stas@zend.com>:

>> <?php
>> namespace Test;
>> // explicitly tell PHP that we want Test::Exception to be autoloaded (in
>> essence)
>> import Test::Exception;
>>
>> class Tester {
>>    public function fail() {
>>        throw new Exception();
>>    }
>> }
>> ?>
>
> This is even better than requiring, and makes the intent very clear.  
> I don't think it decreases intuitiveness, on the contrary - from the  
> look of the code it is immediately clear which exception would be  
> used.

Except that it makes it unclear what happens in _other_ files, which  
is even worse. Once you include the file above, any other file in the  
Test:: namespace that throws an Exception will throw Test::Exception,  
not Exception, even if it doesn't import Test::Exception.

I think it makes much more sense to import classes that are _outside_  
the current namespace. Having to import pieces of your own namespace  
makes namespaces less useful and intuitive.

-chuck