Re: UltraSimple Namespace Solution
| From: | Nathan Rixham | Date: | Sat, 18 Oct 2008 16:31:52 +0000 |
| Subject: | Re: UltraSimple Namespace Solution | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-41255@lists.php.net to get a copy of this message | ||
Gregory Beaver wrote:
Nathan Rixham wrote:I've been flittering between java, as3 and php all week and ended up highly confused, ditsy and using the wrong syntax everywhere - so apologies for my ramblings! cheers for the reply; and thanks for all you're hard work on the namespaces; the RFC you wrote on the wiki really outlined the problem perfectly and made it more accessible to the masses. Many Regards Nath -- nathan ( nathan@kraya.co.uk ) { Senior Web Developer php + java + flex + xmpp + xml + ecmascript web development edinburgh | http://kraya.co.uk/ }seen. Personally though I'd love to see stas' #1 get implemented and "->" used for all functions in a namespace so.. one::step::two(); //always static method of class one::step->two(); //always function of namespace. But it's still ambiguous (only in a rarely though) - if an object with a method "two" is assigned to the static variable of a class called one then problem comes back.First of all, this is not going to happen (voted down). Second of all one::$step is how static variables are accessed, not one::step. So there is no potential for conflict. Greg right enough; there is no conflict *joy*; and it's not introducing any new separator's into php, and I think it makes logical sense /ponders/