> I realize (now) that there is a way to find out which method > resides in which module: http://perl.apache.org/docs/2.0/user/porting/porting.html#Using_C_ModPerl__MethodLookup__to_Discover_Which_mod_perl_2_0_Modules_Need_to_Be_Loaded > but why does this have to be done manually? Why can't there be anAUTOLOAD sub that _by default_ puts a warning in the error log, loads> the right module and just makes the right sub gets called? IIRC MethodLookup does have a 'load all' feature. but other than that, see Apache::porting.
That's fine, but that's introducing bloat (which may not be such a problem with perfork MPM's, but _may_ be a problem with other MPM's, particularly based on Perl 5 ithreads).
Maybe it shouldn't be an AUTOLOAD, but a custom die() handler... ;-)
Anyway, loading these methods on demand may actually be very useful for Perl 5 ithreaded based MPM's!
Liz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
