Edit report at https://bugs.php.net/bug.php?id=36759&edit=1
ID: 36759
Updated by: php-bugs@lists.php.net
Reported by: alexander dot v at zend dot com
Summary: Objects destructors are invoked in wrong order when
script is finished
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: Scripting Engine problem
Operating System: all
PHP Version: 5CVS-2006-03-16 (snap)
Assigned To: cmb
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2021-05-03 11:37:32] cmb@php.net
Is this still an issue with any of the actively supported PHP
versions[1]?
[1] <https://www.php.net/supported-versions.php>
------------------------------------------------------------------------
[2014-03-09 11:55:54] ocramius at gmail dot com
Never mind, I've misread the test and was considering "Bar extends Foo" (isn't
an inheritance)
------------------------------------------------------------------------
[2014-03-09 11:47:58] ocramius at gmail dot com
Is the scope violation supposed to throw a fatal? While discussing with others, it seems like it is
a copy-paste mistake.
It seems strange to me that PHP is not preventing access to that private property in the child
class' __destruct() method.
If it is a copy-paste mistake, then this spawns another bug.
------------------------------------------------------------------------
[2013-02-20 09:12:34] reeze@php.net
Sorry I just try to reproduce, but didn't try the later script.
------------------------------------------------------------------------
[2013-02-20 09:10:49] reeze@php.net
I seems been fixed already, see: http://3v4l.org/b2JWc
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=36759
--
Edit this bug report at https://bugs.php.net/bug.php?id=36759&edit=1