Re: __autoload() enhancement

At 15:18 03/04/2005, Andrey Hristov wrote:

Hi Zeev, the idea one __autoload() may not be capable of loading therefore the next one in the chain should be executed to try to load/define the needed code. bool(false) returned from __autoload() means try with the next in the chain, bool(true) everything went fine skip the rest of the queue.

What I had in mind (primarily to maintain downwards compatibility), is that the engine will check whether the class exists after each call to an autload() callback. If it exists - control returns to the script. If it doesn't - the next autoload() is called. That way we don't need to rely on return values. Either way, though, the order shouldn't matter... Zeev