Re: clarification on the performance of require_once andAPC

Alexey Borzov wrote:

Hi, Lukas Kahwe Smith wrote:

For the performance freak, have a phing tool which strips it out and creates "allfiles.php" (I don't like that name at all).

Stripping out code on the fly in the installer is crazy. We do not want to have magically adapted code versions flying around.

...but we definitely do want to support both "unzip-and-go" and "pyrus-installed" versions of packages, as well as third-party __autoload() implementations. ::snicker::

Yes. At least then we know that its our code running plus some class loading mechanism. Modifying code on install not only poses risk in the actual modification process, but also in other areas like the well known issue that many users report stuff like "on line xyz there is foobar". Your attempted comparison does not hold any water. regards, Lukas