#43442 [NoF->Fbk]: __destruct is calling right after __construct
| From: | johannes@php.net | Date: | Sun, 10 Feb 2008 21:19:08 +0000 |
| Subject: | #43442 [NoF->Fbk]: __destruct is calling right after __construct | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-122163@lists.php.net to get a copy of this message | ||
ID: 43442
Updated by: johannes@php.net
Reported By: cjshark at mail dot ru
-Status: No Feedback
+Status: Feedback
Bug Type: Scripting Engine problem
Operating System: FreeBSD v60
PHP Version: 5.2.5
New Comment:
Check the state of zend.ze1_compatibility_mode
Previous Comments:
------------------------------------------------------------------------
[2008-02-07 14:22:33] info at cvmedia dot de
im on Suse Linux 2.6.22 with php 5.2.5
i get this:
construct
destruct
method!!
destruct
------------------------------------------------------------------------
[2007-12-14 17:07:36] camelot at plevel dot com
im on FreeBSD v6.2
with php 5.2.5 and zend optimiser 3.3
when i turn on zend
i get this
construct
destruct
method!!
destruct
when i turn zend off
i get
construct
method!!
destruct
------------------------------------------------------------------------
[2007-12-11 01:00:01] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2007-12-03 11:14:48] jani@php.net
So what is the configure line you used?
------------------------------------------------------------------------
[2007-11-30 11:00:48] cjshark at mail dot ru
I meen everything is ok under php 5.2.3 and less BUT 5.2.5! Nothing
else is using (search as 3rd party extensions or smth).
------------------------------------------------------------------------
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
http://bugs.php.net/43442
--
Edit this bug report at http://bugs.php.net/?id=43442&edit=1