Mike Seth wrote:
David Zülke wrote:
http://pastie.org/770456
Any objections?
Perhaps it would be better to do this *after* settings.xml and not
before? Reading settings.xml would almost certainly yield
no runtime effects that need something out of the autoload list to be
loaded; on the other hand, autoload.xml may use configuration
values declared in settings.xml. I imagine this is conceivable:
<autoload
name="Dogtrine">/tmp/argh/Dogtrine/%org.rage.wtf.version_that_works_today%/Dogtrine.class.php</autoload>
Oh wait, there's no directive substitution inside the value itself, is
there? Silly me.
In either case if it can be guaranteed that parsing of autoload.xml
doesn't actually cause execution of any third party code that may depend
on settings.xml then I don't think there's a problem.
_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev
