Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41155
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.167 as permitted sender)
Message-ID: <025a01c92fb6$95d8b350$3ffc1f3e@foxbox>
To: <nrixham@gmail.com>,
	"Greg Beaver" <greg@chiaraquartet.net>
Cc: "Stanislav Malyshev" <stas@zend.com>,
	"Lukas Kahwe Smith" <mls@pooteeweet.org>,
	"PHP Developers Mailing List" <internals@lists.php.net>
References: <48F653FF.5010106@chiaraquartet.net> <48F75FA1.7020505@zend.com> <0C55B977-3835-4CB0-A23B-8AA684B71C18@pooteeweet.org> <48F772CD.80600@zend.com> <48F775DD.5010202@chiaraquartet.net> <48F777B4.2050609@gmail.com>
Date: Thu, 16 Oct 2008 18:42:38 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] my last attempt at sanity with namespaces
From: steph@php.net ("Steph Fox")

> after much more thought I think you're option #2 is actually best however 
> the choice of ":::" separator in the example really confuses things and 
> makes at an instant turn off..

This concept was originally presented using the ".." separator, and has been 
presented with others since. The separator isn't the issue with option #2 so 
much as that it's not a familar approach from other languages, and it's not 
particularly intuitive either. I like #2 too, but it's become apparent from 
the voting pattern that people really don't get it. We had a long discussion 
on the list about this exact option using the ':::' separator earlier in the 
week where many agreed to it in theory, but didn't actually recognise the 
exact same proposal when they saw it on the wiki.

I think that pretty much disqualifies it as a solution for ns resolution in 
PHP, sadly. If people on this list aren't able to fully grasp the concept, 
it doesn't have a hope in user space.

- Steph