I use this in a different way so I think it can be useful for everyone 
avoiding long and complex codes.

I´ve got a file called classes.php that looks like:


$Classes = new stdClass();

$Classes->Smarty = BASE_PATH."includes/Smarty/Smarty.class.php";

$Classes->Mail = BASE_PATH."includes/mail/Mail.php";


So my _autoload() looks like:

function MY__autoload($className) {




if (function_exists("spl_autoload_register") ) {


} else {

function __autoload($className) {




Hope it can help you.

""Michael N. Madsen"" <m...@criion.net> escreveu na mensagem 
> Since php started to support oop it has moved more and more features in 
> that direction.
> This is good for me because I love oop. Then came _autoload() and I was 
> rejoiced only to find that this (no fun)ction can't be used to it's 
> fullest potential in oop unless I have all the files in the same 
> directory. This is where you correct me and tell me how I can have a file 
> structure in more then one level and still get the ripe juices of 
> _autoload() (Please, I beg you!)
> I have looked at the comments on the doc page of the function and every 
> single one comes with the addition of many, often complex lines of code 
> that will only add more load on the server. If _autoload can't figure out 
> the correct path to the file which defines the class, then what is the 
> point from an oop pov? 

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to