Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41918
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 74.125.44.30 cause and error)
Message-ID: <491E0297.20108@chiaraquartet.net>
Date: Fri, 14 Nov 2008 16:58:31 -0600
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Marcin Kurzyna <m.kurzyna@crystalpoint.pl>
CC: internals@lists.php.net, Stan Vassilev | FM <sv_forums@fmethod.com>, 
 Stanislav Malyshev <stas@zend.com>,
 Dmitry Stogov <dmitry@zend.com>
References: <49188698.1050505@grudl.com> <49188BD0.9090100@kukulich.net> <4918A3F8.4070809@chiaraquartet.net> <4919A9BD.2020703@grudl.com> <491DE402.4000600@chiaraquartet.net> <72.BB.07308.119ED194@pb1.pair.com>
In-Reply-To: <72.BB.07308.119ED194@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: Namespace resolution rules has been changed?
From: greg@chiaraquartet.net (Gregory Beaver)

Marcin Kurzyna wrote:
> <?php
> 
> namespace foo;
> 
> use bar as A;   /// ->resolves as A == \foo\bar
> use \bar as B;  /// ->resolves as B == \bar
> 
> ?>

Hi Marcin,

Stan also requested this, so it should be considered as a possibility.

Personally, I would rather not introduce this land mine.  It requires
the user to do an implicit prepending of namespace name ("foo") to "bar"
in the use statement as well as a translation of "A", which could fast
lead to unreadable code.

It is probably best to simply require a fully qualified name where it is
intended.  Thus

1) require leading "\" in use statements
2) allow "namespace\blah" in use statements, as this is a valid fully
qualified name.

<?php
namespace my\ns;

// this is a better way to do the suggested "use bar as A;"
use namespace\bar as A;
use \bar as B;

class mine extends \my\parentclass {}
?>

Stas, I'm sure you have an opinion on this?

Greg