Return types for register-hooks and pre-config.

2001-12-12 Thread Harrie Hazewinkel
HI, Some time ago the post_config phase return types was changed from void to int in order detect if a module could not be configured correctly at this phase. I was wondering if there is a reason why this was not done for the register-hooks phase and the pre-config phase?? harrie

Re: Return types for register-hooks and pre-config.

2001-12-12 Thread Ryan Bloom
On Wednesday 12 December 2001 02:14 pm, Harrie Hazewinkel wrote: HI, Some time ago the post_config phase return types was changed from void to int in order detect if a module could not be configured correctly at this phase. I was wondering if there is a reason why this was not done for

Re: Return types for register-hooks and pre-config.

2001-12-12 Thread Harrie Hazewinkel
--On Wednesday, December 12, 2001 2:21 PM -0800 Ryan Bloom [EMAIL PROTECTED] wrote: On Wednesday 12 December 2001 02:14 pm, Harrie Hazewinkel wrote: HI, Some time ago the post_config phase return types was changed from void to int in order detect if a module could not be configured

Re: Return types for register-hooks and pre-config.

2001-12-12 Thread Ryan Bloom
On Wednesday 12 December 2001 02:25 pm, Harrie Hazewinkel wrote: --On Wednesday, December 12, 2001 2:21 PM -0800 Ryan Bloom [EMAIL PROTECTED] wrote: On Wednesday 12 December 2001 02:14 pm, Harrie Hazewinkel wrote: HI, Some time ago the post_config phase return types was changed from

Re: Return types for register-hooks and pre-config.

2001-12-12 Thread Harrie Hazewinkel
--On Wednesday, December 12, 2001 2:32 PM -0800 Ryan Bloom [EMAIL PROTECTED] wrote: Or for instance, the register_hooks fails where some memory needed to be allocated. This function after all gets an apr_pool_t... But we never try to recover from an out of memory error, because it can't