Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41299
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.217.14 cause and error)
To: Steph Fox <steph@php.net>
In-Reply-To: <004701c931de$e7d53460$3ffc1f3e@foxbox>
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> <004701c931de$e7d53460$3ffc1f3e@foxbox>
Message-ID: <F90D55E4-B152-4CE1-A7FA-0C003B7D18BE@prohost.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 18:54:29 -0400
Cc: "Lester Caine" <lester@lsces.co.uk>,
 "PHP internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] Namespace issues
From: ilia@prohost.org (Ilia Alshanetsky)

Another issue I just came across caused by :: being used for both  
namespaces and classes is the fact when it comes to validation such as  
the one I've just put it for constant names, its impossible to  
determine if the prefix is a namespace or a class name. So, I  
definitely think we should change :: to just about anything else, as  
long as its not :: I'd be happy.


On 19-Oct-08, at 7:36 AM, Steph Fox wrote:

> 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
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Ilia Alshanetsky