[dev] Autoloader

Michael J Rubinsky mrubinsk at horde.org
Tue Sep 20 14:01:46 UTC 2011

Quoting Jan Schneider <jan at horde.org>:

> Regarding classmaps, I think the proposed caching autoloader  
> (http://bugs.horde.org/ticket/10396) is even better because it  
> supports 3rd party classes too. (Btw, any feedback on my proposed  
> package solution anyone?)

The proposed packaging solution seems reasonable.

> It could probably be extended to populate it with a pre-generated  
> classmap, though I don't think that the (one-time) slower automatic  
> on-demand population is outweighed by the overhead of having to  
> create classmaps manually. It might even degrade performance-wise if  
> there are a *lot* of packages with classmaps, like in our case.


> Leaves the question whether it would make to add such bootstrap  
> files for 3rd party component consumers. This could indeed be  
> interesting. But as long as this doesn't become a de-facto standard,  
> it's only additional overhead for us (because we won't use it  
> ourselves). If there's a demand for such a thing though, why not.

It *would* be nice to have some kind of bootstrap to make it easier to  
use our libraries without having to rely on Core. The generation could  
probably even be scripted(?)


The Horde Project (www.horde.org)
mrubinsk at horde.org

More information about the dev mailing list