Sándor Tamás (HostWare Kft . ) a écrit :
It isn't really a programming question, but rather a structural.
  It is part of our burden ;)

Which is the better approach:
They are no better approch, only bad ones. I'm using to organize my code in module. Each module require the needed modules. This design permit me to ease case testing, and ease maintenance because you know quite fast what module can be impact by the alteration of another.

I never have to speak about scallability of this method, because I never work on a very big system. But that's optimization, I think it'll need some sed (sed -i 's/\<require_once\>/require_ondemand/' project/) and a strong mecanism to provide including on demand.

--
Mickaël Wolff aka Lupus Michaelis
http://lupusmic.org

Seeking for a position <http://lupusmic.org/pro/>

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to