Please take a look at this new manpage http://perl.apache.org/docs/2.0/api/Apache.html
This issue of ghost Apache namespace troubles me. In mod_perl 1.0 it was OK to have functions like Apache::current_callback() because almost everything was preloaded. I don't think it's OK in mp2. It's absolutely not obvious which module needs to be loaded to get this API, and most people will try to load Apache, and it won't do the trick.
Why not replace:
use ModPerl::Util; my $callback = Apache::current_callback();
with:
use ModPerl::Util; my $callback = ModPerl::Util::current_callback();
then:
use Apache::ServerUtil; my $server_root = Apache::server_root;
with:
use Apache::ServerUtil; my $server_root = Apache::ServerUtil::server_root;
etc. (there are many modules which install things into the Apache:: namespace). i.e. try to use the same namespace as the module the function lives in.
The only obvious need-to-keep is Apache->server, which can really be made a constant too.
or do you think it's OK the way things are right now? The manpage suggests to use http://perl.apache.org/docs/2.0/api/ModPerl/MethodLookup.html to figure what needs to be loaded, but it's not so intuitive.
The only real problem with this change suggestion is backwards compatibility, which is nice to keep small.
__________________________________________________________________ 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]
