Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41250
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.156 as permitted sender)
Message-ID: <001401c930cd$6d106630$3ffc1f3e@foxbox>
To: <internals@lists.php.net>,
	=?utf-8?Q?Pawe=C5=82_Stradomski?= <pstradomski@gmail.com>,
	"Ryan Panning" <rpanning@gmail.com>
Cc: "Greg Beaver" <greg@chiaraquartet.net>
References: <48F653FF.5010106@chiaraquartet.net> <63.BA.57950.BB2A8F84@pb1.pair.com> <200810172220.23260.pstradomski@gmail.com> <48F8FE8D.5000600@gmail.com>
Date: Sat, 18 Oct 2008 03:58:38 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="utf-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: my last attempt at sanity with namespaces
From: steph@php.net ("Steph Fox")

>> I'm just a mere user, but if we go for other namespace separator (be it 
>> ::: or :> or anything else), then I'd rather see it used both between 
>> namespace and class/function/constant name *and* between namespace parts.

OK, so maybe I should explain one little thing about the significance of 
those results: we don't need a namespace separator.

74% of those voters either actively requested or said they could live with 
Greg's option #3. Now, the philosophy that separates that option from Greg's 
other proposals is that it doesn't try to avoid conflict; it accepts that 
there will be ambiguity, and then tries to deal with it.

This is also the approach Stas' proposals take.

No more namespace separator arguments, ever. It was worth it :)

- Steph