Hi!
Once again, no code can trigger the warning right now. As the warning requires a namespace before it can be triggered. Autoload should be declared outside a namespace so that it can load correct namespace classes anyway. So I do not see an issue here.
autoload can work just fine inside namespace as well as outside, there's no problem with that, and class names given to autoloader are always full class names, so where it is declared has no effect.
As for the argument "there's no namespaced code so anything goes since we can't break any code" - it's bogus. We expect a lot of existing code to be converted to namespaces once 5.3 is out, and we want to make it as painless as possible. Throwing warning each time you have include is not the way.
-- 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
