Hi!
Then, if we assume that most people will use the global namespace without prefixing it, what would be the best resolution order for them? (you didn't mention it in your previous message)
Using the prefixed names.
People who care about performance are supposed to profile their code... I guess? If they don't, they probably don't really care about it. People who care about performance are supposed to be knowledgeable about good practices.
I consider knowingly putting performance bomb into the language with the reasoning of "if you know what you are doing, you can disarm it" extremely bad idea, especially in PHP which is supposed to be low-learning-curve language.
Include + relative path does not give any indication either and it does exactly what you've described above (traverse the full include
Include can be cached. Failed autoload can't.
that use __autoload(). With relative paths. Come to think of it, why would an application autoload files that aren't in its directory?
Because there exist applications that have more than one directory, use all sorts of libraries and frameworks, which can have autoloading rules not fit for the scenario when you try to load class which actually is not meant to be loaded. How many of the loaders optimize for the scenario that class can not be found? Not all of them even will survive that.
-- 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
