Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32566
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 38.99.98.18 as permitted sender)
Message-ID: <470295DA.6090602@php.net>
Date: Tue, 02 Oct 2007 14:02:50 -0500
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Benjamin Schulz <php@benjaminschulz.com>
CC:  internals@lists.php.net
References: <A6E970C5-C221-41BE-9229-7C2BD16DC0CF@benjaminschulz.com>
In-Reply-To: <A6E970C5-C221-41BE-9229-7C2BD16DC0CF@benjaminschulz.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: namespaces: import name conflicts with defined class
From: cellog@php.net (Greg Beaver)

Benjamin Schulz wrote:
> Hi all,
> 
> import Foo::Bar AS DomDocument;
> import Foo::Exception;
> import MyStuff::Dom::XsltProcessor;
> 
> Result in a "Fatal error: Import name '...' conflicts with defined class"
> Of course i want to refer to my own exception in my application or
> framework as "Exception", and of course i want to use it without
> prefixes (import myStuff::Exception AS MyStuffException), i wouldn't use
> namespace otherwise (there is no other benefit, right?).
> It's not that one accidentally puts an "import Foo::Exception" in his
> file ..
> 
> Is there a good reason for this bevhaviour that i don't see? There is
> still ::Exception to access the class in the global namespace.
> 
> regards,
> Benjamin

Hi Benjamin,

If you are aliasing a class to the same name as an existing class, you
should also import that class with another name:

<?php
import ::Exception as Notused;
import Foo::Exception;
?>

This is somewhat unintuitive, but is pretty simple to solve.

Greg