Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40687
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <37.20.19781.6B5CBD84@pb1.pair.com>
To: internals@lists.php.net
References: <59.6C.35835.FB3F8D84@pb1.pair.com> <20080924065741.50a30448.kevin@phpro.org> <002701c91dd1$89dad480$3ffc1f3e@foxbox> <bcb7aa500809231617y3305b5bcn18f47630a8124e0d@mail.gmail.com> <CA8D28A3-86A1-477F-B777-93EFC01B71A3@pooteeweet.org>
Date: Thu, 25 Sep 2008 21:09:08 +0400
Lines: 26
Subject: Re: [PHP-DEV] true namespaces, yet another point of view
From: dmda@yandex.ru ("jvlad")

>
> or just leave the organization of things to classes (with long class 
> names with a nice prefix to prevent collissions) and leave it to 
> class_alias() (and equivalent features for functions .. also with the 
> option of a compile time aliasing) to handle the aliasing.
>
> this removes the need for namespaces and use statements, while making  it 
> possible to make class/function names short (that are long for 
> organizational and collision prevention reasons).
>
> regards,
> Lukas Kahwe Smith
>
>
No, you  can't use classes for this. They can't contain the other classes 
and you can't have a class spanned across several files. There are some 
other important differences from the compiler perspecives, but still 
namespaces and classes are containers and you can access their members with 
exactly the same syntax constructs so it's not only possible but reasonable 
to implement them very close to each other, as I suggested in one hashtable. 
As a side effect it will remove the problem with class vs namespace 
ambiguity.

JV