Re: clarification on the performance of require_once andAPC

Alexey Borzov wrote:

If a package has lots of drivers, which most PEAR packages do, it requires both a lot more memory and more processing time to load the single file. Your counter-proposal provides ease to only one audience, those who want a single-file solution for absolutely everything, and does not help those looking for ultimate performance.

How exactly is my proposal different from allfiles.php proposal? I'm not advocating putting a package and all drivers, the user will do: require 'MDB2.php'; require 'MDB2/mysql.php'; as needed. But this will be faster than require 'MDB2/allfiles.php'; require 'MDB2/mysql/allfiles.php'; and easier to remember and type also.

Allfiles.php imho is just a starting point. Generally people that do not care about performance all that much just use __autoload(). Those that do care about performance can use the allfiles.php as a starting point for building a custom include solution. Alfiles.php can also be used for people that just quickly want to try something out without having to define an __autoload() method, but thats really the only reason I ever see anyone actually including this file. regards, Lukas