Re: Namespaces in PHP 6 - ++$take

From: Date: Mon, 20 Nov 2006 19:32:45 +0000
Subject: Re: Namespaces in PHP 6 - ++$take
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-26678@lists.php.net to get a copy of this message
On Fri, November 10, 2006 1:07 pm, Brian Moon wrote: >> Unfortunately namespaces are not only syntactic sugar, but dire >> necessity >> for PHP if it wants to be taken as a serious langauage and defend >> it's >> position against other arising 'web scripting' alternatives. > > It seems the list of things that PHP needs to be "taken as a serious > langauage" is never ending. Before PHP 5, all that was needed was > good > OOP support. Now this. I am for namespaces, but that line is getting > old and I, a professional, serious PHP developer and tired of hearing > it. I was tired of it before the OOP stuff... :-) Honestly, I think PHP's record of usage speaks far more volumes about its quality and utility than any ribbing from "other" language users. I'm reminded of how often we used to rib MS users of how their OS wasn't a "real" OS because it couldn't do X, so they finally fixed it to do X a couple years ago... [Something or other about TCP/IP/SMTP/raw/root access, if you care to refresh my memory...] The end result, though, after they "fixed" it, was that we had a zillion more security holes and viruses because now normal scripts could punch through with this new feature. Anyway, my point is that I also believe namespaces would be "good" for those who need to distribute libraries and whatnot, possibly even more important than OOP was in the first place -- As much of the OOP code is little more than a namespace substitute in the first place. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?

« previous php.internals (#26678) next »