Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41651
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.138 as permitted sender)
Message-ID: <033501c93ea2$ab332690$3ffc1f3e@foxbox>
To: "Stefan Walk" <et@php.net>,
	<internals@lists.php.net>
References: <49048EC1.9060908@chiaraquartet.net> <49107527.7060604@chiaraquartet.net> <02e001c93e9c$a8874f30$3ffc1f3e@foxbox> <200811041819.25933.et@php.net>
Date: Tue, 4 Nov 2008 17:27:43 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] namespace separator and whining
From: steph@php.net ("Steph Fox")

Hi Stefan,

> Dev writes a script, uses autoload, overrides global class.
> Distributed to user, that has ns.lookup=On as you propose, user borks his
> install, lacks the file containing the class, gets the global class ->
> obscure error messages because of nonexisting methods in places unrelated 
> to
> the place where the actual error happened. Not really a good idea, IMO.

This is what happens now, right. So what's different?

> Failing there is the best option. It's not like you have to prefix every
> single occurence, you just have to say at the top of the file "When I say
> Exception, I mean \Exception".

The point is that your dev would have done exactly that, so whether your 
user has the setting on or off is immaterial.

- Steph