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. > 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 - ap_hook_child_init may change to return int as others have - there is no harm in expecting it from perl handlers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
