Comments on: PHP Class Autoload http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/ readers are plentiful, thinkers are rare Fri, 09 Jan 2009 20:52:29 +0000 http://wordpress.org/?v=2.5.1 By: melissa eimers http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3909 melissa eimers Tue, 06 Mar 2007 02:33:26 +0000 http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3909 check out my blog: eimers.blogspot.com check out my blog: eimers.blogspot.com

]]> By: Warren Falk http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3898 Warren Falk Mon, 05 Mar 2007 14:00:32 +0000 http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3898 Including all your files in one central include file might have its benefits, such as allowing more flexibility in naming classes and where class files are stored, and compatibility with PHP4. However, I would think that there could be a large drawback to this in terms of performance for large sites. It could also have a potential impact on distributed development. I get around the issue of having external classes by either using a stub include file for the external classes, or searching multiple folders for classes. And I find that enforcing a naming convention (any naming convention that you can stick to) makes life easier in the long run. Not all who read this will get the inside joke, which is that my sister, the author of the comment, to which I'm replying, is not a programmer and does not, to my knowledge, know any PHP. I was not surprised to see she commented, because she has a reputation for clever humor in comments. But I was quite surprised that her response made sense. I'm flattered that she went to lengths to find an appropriate response even if she did plagiarize it.  Thanks, sis. <a rel="nofollow" href="http://www.weberblogs.com/article.php?story=20041129042029399">http://www.weberblogs.com/article.php?story=20041129042029399</a> Including all your files in one central include file might have its benefits, such as allowing more flexibility in naming classes and where class files are stored, and compatibility with PHP4. However, I would think that there could be a large drawback to this in terms of performance for large sites. It could also have a potential impact on distributed development.

I get around the issue of having external classes by either using a stub include file for the external classes, or searching multiple folders for classes. And I find that enforcing a naming convention (any naming convention that you can stick to) makes life easier in the long run.

Not all who read this will get the inside joke, which is that my sister, the author of the comment, to which I’m replying, is not a programmer and does not, to my knowledge, know any PHP. I was not surprised to see she commented, because she has a reputation for clever humor in comments. But I was quite surprised that her response made sense. I’m flattered that she went to lengths to find an appropriate response even if she did plagiarize it.  Thanks, sis.
http://www.weberblogs.com/article.php?story=20041129042029399

]]> By: melissa eimers http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3870 melissa eimers Sun, 04 Mar 2007 19:31:12 +0000 http://www.warrenfalk.com/blog/2006/08/31/php-class-autoload/#comment-3870 I liked the idea, but had already solved that problem in PHP 4: I included a single file, called "include.php", which had all the include statements I needed throughout my site, whether this particular page needed them all or not. Anyway, I tried the __autoload function instead of the "all-include" file. function __autoload($class_name) { include_once('classes/' . $class_name . '.php'); } Straight away, I hit the problem of calling my php files with all the same name convention. I usually call my classes class.name.php. So In this case I would have to modify the function to include the class. in the front of it. But I don't only include classes in my scripts! I also use functions, and some classes that would not be found in this folder (like the Smarty class). So my decision is to stay away from the __autoload function. Just using an all-inclusive include.php file works much better for me. Just thought I'd say that since no one else has had much to say. I liked the idea, but had already solved that problem in PHP 4: I included a single file, called “include.php”, which had all the include statements I needed throughout my site, whether this particular page needed them all or not. Anyway, I tried the __autoload function instead of the “all-include” file.

function __autoload($class_name)
{
include_once(’classes/’ . $class_name . ‘.php’);
}

Straight away, I hit the problem of calling my php files with all the same name convention. I usually call my classes class.name.php. So In this case I would have to modify the function to include the class. in the front of it. But I don’t only include classes in my scripts! I also use functions, and some classes that would not be found in this folder (like the Smarty class). So my decision is to stay away from the __autoload function. Just using an all-inclusive include.php file works much better for me.

Just thought I’d say that since no one else has had much to say.

]]>