For the record, I agree with Boris on this. Users should never be required to use methods defined in namespaces of modules that they did not explicitly load, and modules should not define things in other namespaces (like the Apache:: stuff that started this thread).
well, there are a few reasons for all of this. granted, it doesn't really make sense before you, well, understand it, but I like it :) so, here's my view on the whole thing...
[snipped the explanation of why being able to load each module separately is a goodness ]
Josh Chamas has suggested some time ago to have a package which will preload groups of modules. So if you don't care about fine tuned performance you could say:
use Apache::whatever qw(:request :server);
and it'll load Apache::Request* and Apache::Server*. We can define more groups.
Still some of these methods return objects which require other packages to be loaded. So dir_config requires APR::Table to be loaded, etc. So I'm not sure how much win this is going to make.
And again, we won't want this Apache::whatever module to be used in CPAN modules, and rather have the authors load explicitly only the modules that really need to.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
