On 10.07.2007, at 18:55, Stanislav Malyshev wrote:
the application should define how things get loaded, precisely
because it decides about what libraries are used, what approach
each of them has taken etc. also on the application level you may
want to implement some way to override implementations from the
library etc.
Why application developer should even care how library is build
internally, let alone override it's loading behavior? These are
exactly the implementation details that should be hidden from the
library user.
because someone needs to decide in what order autoload strategies are
applied. this is especially important for libraries that do not
prefix their class names yet. and like i said its also important to
be able to easily replace a class from a library without having to
muck around with the installed files themselves. if you are
recommending libraries to do all of this themselves, you are handing
a recipe for desaster.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
