Re: true namespaces, yet another point of view
| From: | Lukas Kahwe Smith | Date: | Mon, 29 Sep 2008 06:13:02 +0000 |
| Subject: | Re: true namespaces, yet another point of view | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-40753@lists.php.net to get a copy of this message | ||
On 29.09.2008, at 00:21, Gregory Beaver wrote:
Lukas Kahwe Smith wrote:Well my point was .. Library code uses long names, glue code can alias. Of course sometimes the lines between what is library and glue code are hard to draw. Anyways, I guess we are close to a good solution for namespaces in 5.3 .. regards, Lukas Kahwe Smith mls@pooteeweet.orgOn 24.09.2008, at 01:17, Guilherme Blanco wrote:Hi, This approach doesn't work because aliasing with class_alias() does not allow name conflicts:For those that do not understand very well the explanation of jvlad... He's suggesting to change the class struct to be an scope struct, and have a property that tells if it's a namespace or a class, and reuse the implementation of class which already works very well. The nested support is achieved afai understand through the Adjacency List algorithm... can you confirm this to me?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).