[Sync]

Nice tutorial, very useful!

[callumacrae]

Nice, now I just have to persuade my VPS to accept 5.3!

~Callum

[ShanePerreault]

This answers my question greatly, thanks man.

[Leamsi]

Great tu, might use it sometime

[Kyek]

Nice ;-). Although, you should revisit that autoloader code! I have no idea what the hell I was thinking when I wrote it, because I'm exploding the namespace in order to change the backslash character to a forward slash ... when I could have done a MUCH more efficient str_replace to get the same effect. If you look at the new hydrogen.inc.php, that's the method I use (example from the MVC starter). I also have some fancy footwork in there to make sure the "Class Not Found" error will happen in the file that's 'use'ing a class that doesn't exist, rather than in the autoloader file. That old autoloader adds an embarrassing bit of overhead every time a class is used. (Oh, and the loadPath() function is never called, there -- that's only in the hydrogen autoloader so that other classes can call it)

The giant (giant) benefit of how I do it vs. how most other frameworks do it is that there's no checking to see if a file exists in my code. Doing that check causes multiple stat() calls, which cause hard disk interaction, which is the absolute biggest slowdown for a webapp. So I avoid checks altogether. Preparing for an error wastes time before every include -- not preparing for it but catching the error when it happens only takes time if a file isn't found, which will never happen in production. That's the whole theory Hydrogen is based on ;-).

Not to be a douche, though, but in order to maintain my copyright on Hydrogen, I have to insist that you follow the license if you distribute that code :-/. The copyright notice has to be at the top, or I lose copyright holder control. Sorry man :-/.

[Daniel15]

Looks good. you should add more comments to the autoloader function so we know what it's doing

For what it's worth, this is the autoloader I "made" ("made" because most of the actual work is done by the default PHP autoloader ). Doesn't support namespaces though. Lowercases the class name, splits it up by underscore and looks for it (eg. Test_Class_Blah would correspond to test/class/blah.php):

define('BASEDIR', __DIR__);
set_include_path(get_include_path() . PATH_SEPARATOR . BASEDIR);

/**
 * Load the class specified 
 * @param	string		Class to load
 */
function autoload($className)
{
	/* We're using the built-in autoloader as it's faster than a PHP implementation.
	 * Replace underscores with slashes to use a directory structure (FeedSources_Twitter -> includes/FeedSources/Twitter.php)
	 */
	$filename = strtolower(str_replace('_', '/', $className));
	return spl_autoload($filename);
}

spl_autoload_register('autoload');

Quote

You need to add the following line to any file which uses your classes, if you're using an MVC pattern, this will only be one file.

Not just MVC pattern, but any design pattern. Once you add the autoloader, it should work with anything. I've used autoloaders for tiny projects before, it just makes it easier

Quote

now I just have to persuade my VPS to accept 5.3!

If it's a VPS you should be able to upgrade it yourself

[AwesomezGuy]

Kyek, on 30 January 2011 - 04:57 PM, said:

Nice ;-). Although, you should revisit that autoloader code! I have no idea what the hell I was thinking when I wrote it, because I'm exploding the namespace in order to change the backslash character to a forward slash ... when I could have done a MUCH more efficient str_replace to get the same effect. If you look at the new hydrogen.inc.php, that's the method I use (example from the MVC starter). I also have some fancy footwork in there to make sure the "Class Not Found" error will happen in the file that's 'use'ing a class that doesn't exist, rather than in the autoloader file. That old autoloader adds an embarrassing bit of overhead every time a class is used. (Oh, and the loadPath() function is never called, there -- that's only in the hydrogen autoloader so that other classes can call it)

The giant (giant) benefit of how I do it vs. how most other frameworks do it is that there's no checking to see if a file exists in my code. Doing that check causes multiple stat() calls, which cause hard disk interaction, which is the absolute biggest slowdown for a webapp. So I avoid checks altogether. Preparing for an error wastes time before every include -- not preparing for it but catching the error when it happens only takes time if a file isn't found, which will never happen in production. That's the whole theory Hydrogen is based on ;-).

Not to be a douche, though, but in order to maintain my copyright on Hydrogen, I have to insist that you follow the license if you distribute that code :-/. The copyright notice has to be at the top, or I lose copyright holder control. Sorry man :-/.

Yeah I did revisit the file, but I noticed a whole load of extra things with HYDROGEN written in them, and I decided to not bother putting it here until I'd tested using it myself, otherwise the tutorial would be useless.
I'll go get your license thingy and readd it once I'm on my computer, I didn't actually remove it, just I only copy pasted the class into my own include file, and from that is where I got the code for the guide. So there's no problem readding it.