If all you are doing is allowing a colon in the name and renaming all the functions from str_foo to str:foo, I see this as complete pointless, only increasing the wtf factor. And requiring everyone to rewrite their scripts.
Ilia Jessie Hernandez wrote: > Hi Ilia, > > While it really doesn't matter to me if functions are namespaced or not, or > even if functions are allowed inside namespaces, I just want to clarify > that only one hash table lookup would be done (as I said in my previous > post, this change was very simple, but all it did was allow the use of > colons in function CALLs). The colon would be part of the function name, > that's why no performance would be lost. > > > Regards, > > Jessie > > > Ilia Alshanetsky wrote: > > >>Why would I need name spaces for basic functions, just so that I need to >>rename all my code to use str:replace rather then str_replace and >>perform 2 hash table lookups? >> >>Ilia >> >>Marco Tabini wrote: >> >>>Hey Ilia, >>> >>>On 8/12/05 3:03 PM, "Ilia Alshanetsky" <[EMAIL PROTECTED]> wrote: >>> >>> >>>>-1 to namespaces. As for modifying functions that would require a fair >>>>number of function aliases for BC as untold number of scripts will >>>>break. That is something we are trying to eliminate in the first place. >>>> >>> >>> >>> >>>With namespaces, wouldn't the problem go away altogether? Old function >>>names can be deprecated and E_STRICT'ed and a new, uniform naming >>>convention and parameter order be enforced for the future. I hate >>>namespaces but this sounds like a good solution to me. >>> >>> >>>Mt. >>> >>> >>> >>> > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
