Re: 5.0.5
| From: | Scott MacVicar | Date: | Tue, 06 Sep 2005 13:37:34 +0000 |
| Subject: | Re: 5.0.5 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18691@lists.php.net to get a copy of this message | ||
Zeev Suraski wrote:
> If there are no (ultra last) objections, I'll roll 5.0.5 tomorrow
> morning (.il/Europe time) and post it in the evening.
>
> Zeev
I'm still objecting to a patch by Jani made in April to move destructor
before shutdown functions. It was in response to the following report,
http://bugs.php.net/bug.php?id=30578
The problem being other than the fact that it's broken some BC is that
when it comes around to using the shutdown function any objects you
might actually have wished to use have since had their destructor called
closing connections and finalising data.
All I am proposing is that the shutdown function is run prior to
destruct functions being called as I don't expect to still be able to
access objects after the destructor is called which is still the case.
Changing the order doesn't effect bug 30578 which it was fixing.
The attached code demonstrates the problem, I'd expect to get the
following output
__construct
execution
execution
__destruct
the shutdown function checking the last step run, unfortunately I get
__construct
execution
__destruct
__destruct
Even though the destructor has been called I can still access the object
and fetch the value of the step variable.
Scott