Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32617
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <4704006E.6040104@zend.com>
Date: Wed, 03 Oct 2007 13:49:50 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Greg Beaver <greg@chiaraquartet.net>, Dmitry Stogov <dmitry@zend.com>
CC: php-dev <internals@lists.php.net>, 
 Benjamin Schulz <php@benjaminschulz.com>
References: <4703F1A1.6020906@chiaraquartet.net>
In-Reply-To: <4703F1A1.6020906@chiaraquartet.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] a way to fix the import issue
From: stas@zend.com (Stanislav Malyshev)

> <?php
> namespace Foo;
> import Blah::Exception;
> $a = new Exception;
> ?>
> 
> should in fact be implicitly importing Blah::Exception as if it were
> Foo::Exception, rather than as ::Exception.  In other words, I would
> actually expect the above code to be equivalent to:
> 
> <?php
> namespace Foo;
> import Blah::Exception as Foo::Exception;
> $a = new Foo::Exception;
> ?>

No, not really. It's equivalent to:
<?
$a = new Blah::Exception();
?>

There's no class named Foo::Exception and import does not create it. 
However, I think I see what you were meaning - that new Exception should 
refer to Blah::Exception. I think it is true. Dmitry, could you look 
into it? I.e. unqualified lookups inside namespace should also take 
imports into account.

-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com