Hi!
It seems that we're not quite 100% how we want to do things. Reading the "Namespaces with functions/constants" part of Stas' RFC makes me cringe... just changing the behavior of -> and :: to just make things work is a cludge, and a bad one at that. The other part, "Namespaces
I think that's actually what we should have done from the start. All OO languages but C++ have same operator for both static and dynamic OO access, and C++ is not exactly clarity example anyway. But we have the baggage of being used to C++ way, so...
However, while reading code it makes it absolutely clear whether you're using an internal class or not.
it is always absolutely clear - if you didn't say :: you are not.
As we're getting really close to 5.3, I would suggest to remove namespaces from this release as we're simply not done with even agreeing on how things should work. PHP 5.3 has many other cool things, and
You realize this means PHP will never have namespaces, right?
Unicode). We've done with namespaces for a loooong time, and they've never really been *required*. Many people won't be able to use it any
For you, maybe, but for other people out there they are.
If we *absolutely *have* to* have namespaces, then we should go with the "Namespaces without functions/constants" proposal, with some tweaks.
Which tweaks? -- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
