> What I really find annoying, is that when you're porting, things start > to fail.
agreed. that's even the basis for the mp2 talk I've been giving and the article I wrote for perl.com - porting is lots more frustrating than we sometimes make it out to be. > 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 an > AUTOLOAD 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. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
