Because the require_once() is conditional, it's not actually seen as a straight forward include (you can't predict whether to require the file until that code block is executed). As a result, although the file is cached, the class/etc. in it are done so separate to the main code. Net result is that the cache is not as effective. In essence, autoloading
Can you explain on that - do you mean that the cache you are talking about caches the whole sequence of the included files as a single block and needs to predict which files are included and which are not? Could you point to the opcode caches that act this way? IMO it's very wrong way for the opcode cache to act, but I'd like to know which ones do that.
-- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/
