Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40737
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <81.6B.30545.B4C3ED84@pb1.pair.com>
To: internals@lists.php.net
References: <9E3A4397-3595-42D8-BF73-7F7575B93772@pooteeweet.org> <003501c92037$9512fef0$3ffc1f3e@foxbox> <48DD7E3D.5060708@zend.com> <006701c92039$6245dc20$3ffc1f3e@foxbox> <48DDB24A.7090705@chiaraquartet.net>
Date: Sat, 27 Sep 2008 17:59:36 +0400
Lines: 22
Subject: Re: [PHP-DEV] alpha3
From: dmda@yandex.ru ("jvlad")

> Adding support for functions, constants and even variables is actually
> quite do-able with the solution I suggested (different separator between
> namespace name and function/constant/variable name) and can be added 
> easily.

> Adding support for functions, constants and even variables is actually
> quite do-able with the solution I suggested (different separator between
> namespace name and function/constant/variable name) and can be added 
> easily.


Greg,

Does it mean that the namespace separator will not be (or likely not to be) 
the same when you need access to namespaced classes vs namespaced functions? 
What's about consistency of the design? If you can't resolve the ambiguity 
or any other problems around namespaces without changing the separator, why 
not to change it for classes too?

-JV