Namaspaces, caling functions and classes defined in the global name space
- From: taps128 <nstjelja@xxxxxxxxx>
- Date: Fri, 30 Nov 2007 08:30:29 +0100
I've been reading the namespace specification for the 5.3 relaese, and I can't stop thinking that they have complicated the thing unecessary. Here is what I mean.
So far if you call a function or a class in (which is not global ) using this:
::A::foo();
it will first try to run the function foo() from the namespace A , and if it can't find it it will run the static method of the class A from th e global namespace.
I can't stop thinkign this is to complicated to read. Wouldn't be simple to just use the GLOBAL keyword for the global namespace, so this:
A::foo() will run the function foo from the A namespace, and this GLOBAL::A::foo() will run the static mehod foo of class A from the global namespace.
.
- Follow-Ups:
- Re: Namaspaces, caling functions and classes defined in the global name space
- From: Toby A Inkster
- Re: Namaspaces, caling functions and classes defined in the global name space
- Prev by Date: Re: Groovy/Grails vs PHP for scalable web site dev
- Next by Date: How to get PHP function status?
- Previous by thread: php mail() not sending to mail Clients (ie, Outlook, Apple Mail, thunderbird, etc..)
- Next by thread: Re: Namaspaces, caling functions and classes defined in the global name space
- Index(es):
Relevant Pages
|
