2008/10/17 Mike Willbanks <[EMAIL PROTECTED]>: > 1. #3 - it is much cleaner to read than the other implementations in > resolving the conflict. a different separator will be much harder to simply > see from a comparison.
I beg to differ. A different separator (namespace scope resolution operator) gives immediate feedback about a statement, e.g. "foo:>bar()" is unambiguously a call to function bar() from namespace foo, whereas a solution based on top-level declarations requires to go back possibly 1000's of lines above the statement to check whether "foo::bar()" is a call to static method bar() of class foo, or function bar() of namespace foo. To put it in other words, when you're reading line #1234 of a script, you can't be sure of what foo::bar() does unless you clearly remember the "use" statements at the top of the file or go back to check them. Not to mention that you also need to remember the top declarations or remember which aliase(s) you gave to "foo" as a namespace and "foo" as a class, if you're using both in the same file. JD -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
