1) adds "unset import" syntax for declaring a namespace to have local import scope (it does NOT affect variable scope or the global class/function table)
I don't like it. What's "unset import"? Seems to be very artificial concept.
be as intuitive as possible. Having a separate scope by default for import that does not inherit from the global scope is not very intuitive.
Yep, it isn't. But it's the only concept that we saw so far that is consistent and logical.
So, instead of resetting current_import by default, this patch makes import global by default and local by explicit syntax via:
But this syntax, unfortunately, doesn't make it better. If the user would have to manually control all the imports it'd be very irritating. And what if he wants to keep one import and not keep another?
Also, the problem of namespace being influenced by external code still not solved.
-- 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
