Volker Dusch’s Blog: Autoloading for legacy, non-framework projects

In his latest post Volker looks at something he sees more and more projected implementing as a simple way to not have to manually define paths all over their applications – creating autoloaders. His post shows how to create one such autoloader for a legacy, non-framework type of project.

The first argument usually is “ease of use”. It can get pretty annoying when you have to clutter your whole application with “require this file here and that file over there” statements. […] The main motivation for autoloading usually is “getting rid of all the require statements and the problems resulting from forgetting one at one point where you don’t notice it because on your machine it worked.

In some projects you’re lucky enough to have class name to file name mapping to make it simpler. His project didn’t have that, so he needed a way around it. His answer came in the PHP Autoload Builder tool – a handy command line script that works through your code and builds an index of sorts you can refer to for the correct class-to-file map.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: