Hi!
namespace A { code }namespace B { code } code seems equivalent to
Again, my point exactly. The above construction - which {} syntax encourages you to use - should never be used at all!
My point is that if we are going to allow multiple namespaces per file solely on the perspective of permitting packaging, we should also allow mixing namespaced and non-namespaced code for that same perspective, and the current syntax is not going to allow that.
Why should we? I don't think we should. Yet less we should encourage it. In fact, I already regret we allowed it in first place - despite dozens of explanations, even the members of the core PHP team seem to be unable to understand seemingly simple concept that this is to be used only for packaging. Somehow the idea that it is the preferred way to use namespaces seems to be one many people are stuck to. So what happens when they start educating other users - I'm afraid to imagine. I suspect this feature would be abused on the large scale.
-- 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
