Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40586
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain iamjochem.com from 194.109.193.121 cause and error)
Message-ID: <48D59477.90801@iamjochem.com>
Date: Sun, 21 Sep 2008 02:25:27 +0200
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Steph Fox <steph@php.net>
CC: RQuadling@GoogleMail.com, 
 PHP Internals List <internals@lists.php.net>
References: <48D47532.8080102@chiaraquartet.net> <e666c3890809200924t28f1c585kad77729dd608c5ad@mail.gmail.com> <10845a340809201643q59e27211i471e09241f7253b1@mail.gmail.com> <003301c91b7c$b2552930$3ffc1f3e@foxbox>
In-Reply-To: <003301c91b7c$b2552930$3ffc1f3e@foxbox>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] solving the namespace conflict issues between function/static
 method class constant/ns constant
From: jochem@iamjochem.com (Jochem Maas)

Steph Fox schreef:
>> Seems like a winner. Just a whole ton of BC though for those using #
>> for comments.
> 
> Yep, so forget it. Or were you doing a Jani? ;)

It seems to hav escaped everyone that Greg's latest proposal doesn't change
the namespace seperator token, instead it comes with a new concept of namespace
member [token].

ambiguity related to the 'use' statements remains regardless of what the namespace
seperator is ... therefore the proposal for a new operator that allows to explicitly
reference namespace members:

<?php

use my#funky#namespace#strlen; // is this aliasing a class, function or namespace?

strlen(); // is this interal strlen() or namespaced function?

?>

and obviously BC dictates that '#' cannot be considered, but that's moot anyhow.


> - Steph
> 
>