Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41242
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <05FD6ACC59464F8799DE54EBBB038B3D@pc>
To: "PHP Developers Mailing List" <internals@lists.php.net>
References: <48F653FF.5010106@chiaraquartet.net> <48F7D0F6.20707@macvicar.net>
Date: Fri, 17 Oct 2008 21:58:43 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] my last attempt at sanity with namespaces
From: sv_forums@fmethod.com ("Stan Vassilev | FM")

> Regarding internal class resolving, it seems logical but will slow down
> resolution within namespaces. But I doubt this is much of an issue as it
> doesn't affect those not using namespaces.

I don't think that makes sense to say "it doesn't affect people not using 
namespaces" when talking about namespace design.

I believe internal classes should be explicitly disambiguated, even if it 
looks ugly, so the autoloader can occur at the right place in the chain. 
Anything else would make namespace+autoload an unusable combination.

Greg, good work on the proposals but I think there's some confusion, even 
among core devs about the nitty gritty details on some of the proposals. I'd 
be nice if we can add "allowed / proper" and "not allowed / wrong" examples 
and such to the RFC-s so it's more obvious what impact each proposal has on 
code.

As for ::: vs ::, those are virtually not distinguishable in a lot of code, 
so if that's to go, pick another syntax. ":>" is fine, "\" is fine, ".." is 
fine.

Regards, Stan Vassilev.