Re: Namespace issues

The N word discussion looks neverending... solution #3 from Gregory solves the ambiguity so I dont see how it will "create such nightmares in big projects with ambigous identifiers". I'm using the :: operator for the last 6 months and I had no such issues even without the fix (I'm not naming classes and namespaces in the same way, and I dont see why I would need to do so). Have you tried using it? If the __autoload performance problem is solved I dont see what is the problem with the current separator. I would wait for the opinion of Gregory and Stas Malyshev on this matter. On the other hand I dont think the backslash is ugly, and I think that the windows users will find it somewhat familiar for using it in tree structures like the namespaces. On Tue, Oct 21, 2008 at 10:33 AM, Stan Vassilev | FM <sv_forums@fmethod.com>wrote: > > Hi, > > Guys, this is like junior school in here. > > Let me put some things in perspective: > > 1) The location of backslash on foreign keyboard is entirely irrelevant for > the choice of namespace separator. Why? You already use this *every day* to > escape characters in your strings and regular expressions. Anyone complained > about the location of backslashes in there? No. > > 2) Where the backslash is, is also where the {} and [] are on those > kayboards, as some people already said. > > 3) "Backslash is ugly" <-- are you honest? Which is uglier: :::Foo() > ::Foo() or \Foo(); The last one at least has intuitive meaning (like file > paths: absolute path). Face it that you'll be typing either one of the above > three a *lot*, and pick one that makes sense visually and for newcomers > alike. I think that's the backslash. > > 4) "But we want the same operator". Well? I want a pony, the fact is > however, the other languages have the design to afford the same separator > for namespaces, static methods and members. Shoehorning this in PHP while > maintaing BC will create such nightmares in big projects with ambigous > identifiers, autoload performance issues, that you'd wish you go back and > change the damn namespace operator to just about *anything* but "::". > > I wish the people who have a clear opinion of the above voice their > opinion. For those who aren't quite sure what the issues in point 4 are, > please just stay low and follow the list until you do. > > Regards, > Stan Vassilev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Vesselin Kenashkov developer at www.webstudiobulgaria.com