Re: autoload, include_once naming conventions

Stephan Schmidt wrote:

It would be nice to be able to pass a second parameter that defines the 'type' of the class. In several of my projects, I'm using code like: Factory::addClassLocation('Component', '/path/to/custom/components'); Factory::addClassLocation('Component', '/another/path'); Factory::addClassLocation('Filter', '/path/to/custom/filter'); Factory::loadClass('Component_Foo', 'Component'); The class loader then will check, whether the class exists in the custom folder and if it's not found, it checks in the default location. This is nice of you are writing custom drivers for any PEAR class. If this class then uses the class loading mechanism, the user is able to add new paths for the classes.

just a note: generally however I dont want to take away the power of include_path though. its very nice way for the user to stick an include_path infront of the pear path to easily override code from pear. regards, Lukas