Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.154 cause and error)
Message-ID: <064401c836de$e49dde10$e6dfc350@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Stanislav Malyshev" <stas@zend.com>,
	"Gregory Beaver" <greg@chiaraquartet.net>
Cc: "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>
Date: Wed, 5 Dec 2007 01:33:47 -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")

>> However, in the global scope (no namespace) it would fail.  This is a
>> bug that is easily fixed.  use should allow re-aliasing of global
>> classes, and I could provide a very easy fix.
>
> This is not a bug - since there you work with test::xmlreader, which of 
> course you can define. But in global space you'd work with existing name 
> xmlreader, which would be redefined. And PHP never allowed redefining 
> classes.

I'm truly glad you said that's not a bug, my world just started to make 
sense again. But Stas, consider (old dialect bc I need to update locally 
sorry):

import nstest::test as whatever;

This works in the global space, right? Now along comes, say, Pierre or 
Derick or Marcus with this class they just have to add to an existing 
(non-namespaced) core extension, and the obvious and perfect name for this 
class happens to be 'whatever'. I upgrade PHP and suddenly I start seeing

Fatal error: Import name 'whatever' conflicts with defined class in ...

Now sure, I can fix that. I can search and replace all my instances of 
'whatever' in my code. How is that different from what we had before?

Greg would say I should've namespaced this file, I know... but it's possible 
to use import (OK, 'use' now) in the global space, so how are you going to 
prevent people from doing that?

- Steph