Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41276
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.179 as permitted sender)
Message-ID: <004701c931de$e7d53460$3ffc1f3e@foxbox>
To: "Lester Caine" <lester@lsces.co.uk>,
	"PHP internals" <internals@lists.php.net>
References: <48F89F19.9040405@croscon.com> <48F8D221.4090805@rowe-clan.net> <610432496.20081018230350@marcus-boerger.de> <798986500.20081018235654@marcus-boerger.de> <6F.F1.37817.AC67AF84@pb1.pair.com> <48FADBF9.1030704@lsces.co.uk>
Date: Sun, 19 Oct 2008 12:36:17 +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] Namespace issues
From: steph@php.net ("Steph Fox")

Hi Lester,

> And there are no problems with those on foreign keyboards?

If there are, those foreign keyboards are unable to offer either escaped 
chars or MS paths... which seems highly unlikely.

> But do I still understand that there is an alternative method that was not 
> part of this last round of voting? And needs to be reviewed in light of 
> the current 'consensus' ?

It was linked from Greg's proposals too: 
http://wiki.php.net/rfc/namespaceref. Basically (assuming that we're saying 
we want ns support for functions/constants) Stas avoids the need for a 
second ns separator by using the syntax

Name->Member

for static access. The 'avoid the need for second ns separator' part of 
Stas' proposal has widespread support according to the poll, it's just a 
case of figuring a way to manage this without introducing ambiguity into the 
code.

Both Stas' proposal and Greg's option #3 are flawed in that way (either to 
humans or to the Engine), so the search is on to find a solution that isn't 
ambivalent to either - always assuming it's possible.

- Steph