Question

I have read about dynamically loading your class files when needed in a function like this:

function __autoload($className)
{
   include("classes/$className.class.php");
}

$obj = new DB();

Which will automatically load DB.class.php when you make a new instance of that class, but I also read in a few articles that it is bad to use this as it’s a global function and any libraries that you bring into your project that have an __autoload() function will mess it up.

So does anyone know of a solution? Perhaps another way to achieve the same effect as __autoload()? Until I find a suitable solution I’ll just carry on using __autoload() as it doesn’t start becoming a problem until you bring in libraries and such.

Thanks.

Answer 1

I have used the following code to use spl_autoload_register in a way that it will degrade if it isn’t present, and also handle libraries that use __autoload, that you need to include.

//check to see if there is an existing __autoload function from another library
if(!function_exists('__autoload')) {
    if(function_exists('spl_autoload_register')) {
        //we have SPL, so register the autoload function
        spl_autoload_register('my_autoload_function');      
    } else {
        //if there isn't, we don't need to worry about using the stack,
        //we can just register our own autoloader
        function __autoload($class_name) {
            my_autoload_function($class_name);
        }
    }

} else {
    //ok, so there is an existing __autoload function, we need to use a stack
    //if SPL is installed, we can use spl_autoload_register,
    //if there isn't, then we can't do anything about it, and
    //will have to die
    if(function_exists('spl_autoload_register')) {
        //we have SPL, so register both the
        //original __autoload from the external app,
        //because the original will get overwritten by the stack,
        //plus our own
        spl_autoload_register('__autoload');
        spl_autoload_register('my_autoload_function');      
    } else {
        exit;
    }

}

So, that code will check for an existing __autoload function, and add it to the stack as well as your own (because spl_autoload_register will disable the normal __autoload behaviour).