Stas Bekman wrote: > 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.
well, I agree with you about the Apache:: namespace. but the "not obvious" part applies to lots of other things as well - it's also "absolutely not obvious" that you need to load Apache::RequestUtil to get $r->dir_config to work :) > > Why not replace: [snip] > The only obvious need-to-keep is Apache->server, if we're going to keep Apache->server around then I don't see a reason for changing other Apache:: class methods/functions - either remove the Apache namespace completely, or make it more intuitive by creating a real Apache class (.pm, .xs and other required glue) where all these obscure methods live. > which can really be made a constant too. I hadn't considered that, but you're absolutely right. > > 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. MethodLookup is really sweet, but it's not intuitive that you need a separate module to tell you what to load. > > The only real problem with this change suggestion is backwards > compatibility, which is nice to keep small. well, I feel less strongly about this than you do. the few methods that live in Apache:: land are small compared to all the other adjustments users are already required to make. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]