On Tue, 10 Jul 2007, Stanislav Malyshev wrote: > > > Well if we are speaking of best practices, the sensible thing for > > > libs to do is to provide a function/method users can call inside > > > their own __autoload() implementation. This way users are free to > > > make their __autoload() work as they please/require. > > That's OK too, but this requires the user to always implement > __autoload. And now what happens if this module is aggregated into > other application?
The application should define this, not the library or module... Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
