Re: REGISTER_SHUTDOWN_FUNCTION() BUG -- Please Fix.
| From: | Jason Caldwell | Date: | Tue, 17 Sep 2002 16:42:53 +0000 |
| Subject: | Re: REGISTER_SHUTDOWN_FUNCTION() BUG -- Please Fix. | ||
| References: | 1 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-15864@lists.php.net to get a copy of this message | ||
It's a bug. spoke to Rasmus at some length about just before i posted it in
the bug report.
The online help page is inaccurate in describing the full functionality of
the function:
http://www.php.net/manual/en/function.register-shutdown-function.php
REGISTER_SHUTDOWN_FUNCTION() is suppose to kick-off when any one of the
following things happen -- Exit, Error, TIMEOUT or User Abort.
According to Rasmus, the TIMEOUT functionality of this function works fine
under Linux -- however, it's not working under Win32 !
There apparently is another bug with this function -- you are suppose to be
able to call more than one REGISTER_SHUTDOWN_FUNCTION(), and they are
suppose to executed in-order... some people are reporting that only the
first encountered REGISTER_SHUTDOWN_FUNCTION() is executed, then the script
exits.
Someone needs to go through this function, pretty thoroughly, and get it
working correctly. Being able to run code on a timeout, user-abort or error
is critical.
Jason
"Jason Caldwell" <jason@thinkingman.org> wrote in message
news:20020917072621.48184.qmail@pb1.pair.com...
> I'm posting this here to give this BUG attention. It's a pretty serious
one
> for Win32 users, and it would be great if it could be fixed *very
> quickly* -- I posted this in the Bug Reports on PHP.net on May 27th, 2002.
>
> Here's the link: http://bugs.php.net/bug.php?id=17461
>
> I need to use this function to perform certain *required* tasks on a
> Timeout -- however (and please read the Bug Report, before replying) the
> Timeout functionality of this function DOES NOT work on Win32 builds.
>
> If your a C/C++ / PHP contributor and have a moment to look into this --
it
> would be great -- I would love to see this fixed in release 4.2.4 !!!
>
> Thanks
> Jason
>
>