Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33711
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.131 cause and error)
Message-ID: <06b001c836ee$e1097970$e6dfc350@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Gregory Beaver" <greg@chiaraquartet.net>,
	"Derick Rethans" <derick@php.net>,
	"PHP Developers Mailing List" <internals@lists.php.net>
References: <alpine.DEB.0.98.0712042315260.20300@kossu.ez.no> <4755E492.2080906@chiaraquartet.net> <4755FD27.3030802@zend.com> <064401c836de$e49dde10$e6dfc350@foxbox> <4756044D.5000803@zend.com> <066f01c836e2$4a209fe0$e6dfc350@foxbox>
Date: Wed, 5 Dec 2007 03:28:15 -0000
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: RFC: Dropping Namespace
From: steph@zend.com ("Steph Fox")

> I guess what I'm really asking is, 'is there any point in allowing 
> import/use to be used in the global space?' I'm tired and etc, but I just 
> can't visualize where it would be useful.

And now I've finished reading old South Park episodes...

OK, it's sinking in now. Because global import/use is something you only 
have to type once, whereas you'd have to add the namespace declaration, the 
relevant includes and any specific imports from the global namespace on a 
per-file basis (unless that last is a bug in my ageing PHP copy).

Sorry, I'm slower than the average glacier tonight :(

Even so... if you want your code to be safe from potential naming collisions 
you'd need to do all that stuff _anyway_, so what's the point in having a 
quick and dirty way to be unsafe? What am I missing here? Surely if people 
don't want to utilize namespacing in their own code they should just stick 
with fully qualified names?

I'm asking a lot of questions because I'd _like_ this to work, I just don't 
see it as working if it's possible to break a namespaced application with 
third-party changes. To me that's the main reason for having namespace 
support in the first place, and without it, namespace support is just a way 
to prettify names.

I'd like wildcard support too... and support for multiple namespaces per 
file (for bundling only)... but neither of those are complete deal-breakers 
in my eyes. Protection from naming collisions, is.

- Steph