Re: Alternative to multiple namespaces per file

From: Date: Sat, 31 May 2008 17:01:08 +0000
Subject: Re: Alternative to multiple namespaces per file
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-38034@lists.php.net to get a copy of this message
On Saturday 31 May 2008, James Dempster wrote: > I would agree with you, I think namespaces should wait for a later version. > Maybe 6 or even later. I believe there are many problems that need to be > sorted be namespaces hit release. > > Maybe we could do something like so. > > namespace Fully::Qualified::Class::Name class Declaration extends Whatever > implents MyInterface { } > > I have reservations in using :: as a resolution operator which can easily > clash with normal class space usage. > > Is it too late to have these discussions?? It seems I missed the big > namespace discussions on the mailing list and things have already gone > ahead. > > /James Unfortunately it probably is. I recall someone did raise the ClassName::staticMethod() vs. Namespace::function() collision problem months ago, and the response at the time was "Pfft, like who uses classes and functions in the same project, anyway?" (Of course, the answer is "well I do" but I've long since learned that such answers don't carry much weight around here, so I mostly just read to see where the language is going rather than to influence it. So I've just resigned myself to not being able to use namespaces in PHP.) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson

« previous php.internals (#38034) next »