Re: [PHP-DEV] Mod Deinit Not Called if Bad Cmdline Option [PATCH]

2006-06-13 Thread Steph Fox
Hi Michael, Actually it's not true either... what made you think that, Michael? Care to describe what you're seeing? Consider the following php script: #!/usr/bin/php -q -c foo No, the script is reached OK - it's just that Zend thinks your php.ini filepath is 'foo' as well as your file,

Re: [PHP-DEV] Mod Deinit Not Called if Bad Cmdline Option

2006-06-13 Thread Michael B Allen
On Tue, 13 Jun 2006 05:45:26 +0200 "Steph Fox" <[EMAIL PROTECTED]> wrote: > Actually it's not true either... what made you think that, Michael? Care to > describe what you're seeing? Consider the following php script: #!/usr/bin/php -q -c foo http://www.ioplex.com/ -- PHP Internals - PHP

Re: [PHP-DEV] Mod Deinit Not Called if Bad Cmdline Option

2006-06-12 Thread Steph Fox
Actually it's not true either... what made you think that, Michael? Care to describe what you're seeing? Good question. Is module startup already called at this point? Is there a reason why you care? At 11:34 AM 6/10/2006, Michael B Allen wrote: If php exits due to a bad commandline option

Re: [PHP-DEV] Mod Deinit Not Called if Bad Cmdline Option

2006-06-12 Thread Andi Gutmans
Good question. Is module startup already called at this point? Is there a reason why you care? At 11:34 AM 6/10/2006, Michael B Allen wrote: If php exits due to a bad commandline option it never calls module deinitialization routines. Is that a bug or a feature? Mike -- Michael B Allen PHP Ex