I would probably be in favor of throwing a notice or a warning when someone modifies a built-in function (or even throw an exception) and
What's the use of having feature that produces an error when used? Anyway, it won't help you since you could have global function defined later than namespaced function.
We could change resolution rule to look for global names first, but it's not that clear to me it's what we really want - for example, it would not allow one to use Exception class in namespaces - since there's already such global class.
I think having namespaced entity with the same name as global entity may be both desired and undesired in different contexts, and there's an easy way to deal with it unambiguously - just use ::name for global names.
Also we suppose that people are in control of their namespaces - i.e. that you know what classes/functions your namespace contains.
-- 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
