-----Ursprüngliche Nachricht-----
Von: Stanislav Malyshev [mailto:stas@zend.com]
If the class for which autoloaded request is issued exists.
However, we are discussing the case where this class does
not exist, so it can not be loaded. Thus, autoload request
will be repeated on each access to such class.
Just a quick idea - what if requiring that autoloaders behave deterministically, that is, once a certain autoloader implementation has been given the possibility to find a class it will never be asked again (because it wouldn't find it later on either).
That might allow for caching the decision, so the next time you hit the same unqualified name you know what is meant? Does that make sense?
-mp.
Just a quick idea - what if requiring that autoloaders behave
deterministically, that is, once a certain autoloader implementation
has been given the possibility to find a class it will never be asked
again (because it wouldn't find it later on either).
I'm not sure if it's a correct assumption to make in general case -
files can be created.
--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com