Doug MacEachern wrote: > On Thu, 6 Jun 2002, Stas Bekman wrote: > > >>The problem: PerlChildInitHandler handler runs in the parent instead of >>the child > > > fixed. also fixed the OpenLogs issue with the same change.
confirmed. Thanks! Should the + in: Perl<>Handler +Foo work? >>Also ap_hook_child_init() doesn't expect any return value, why does >>PerlChildInitHandler? 1.x's version doesn't require it. 2.0's prints >>undef warnings if the value is not returned. > > > - it easier to use the same prototype for generated code and the generic > callback handler > - the modperl 1.x version does in fact check return codes the same way yes, but it doesn't seem to complain if the return code is not supplied. tested with PerlChildInitHandler > - ap_hook_child_init may change to return int as others have > - there is no harm in expecting it from perl handlers ok. __________________________________________________________________ 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]
