ID: 27903 Updated by: [EMAIL PROTECTED] Reported By: schroeter at liquidvision dot net Status: Bogus Bug Type: Class/Object related Operating System: Winn2000 Server PHP Version: 5.0.0RC1 New Comment:
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php This is correct behavior, nothing we can fix most likely here for PHP 5.0. Previous Comments: ------------------------------------------------------------------------ [2004-04-07 07:57:43] [EMAIL PROTECTED] You need to redesign your stuff, the destructor works just fine. (don't misuse it like you did) ------------------------------------------------------------------------ [2004-04-07 07:04:36] schroeter at liquidvision dot net Description: ------------ The __destruct() method seems buggy as the destructor is called after some system internals are already cleaned up (e.g. mysql extension, session etc.). Thus it is impossible to set e.g. session data in the destructor, leaving this mostly superfluous! I have prepared an example that shows the point in detail. This is also true for e.g. mysql_close() in the destructor! Reproduce code: --------------- http://www.liquidvision.net/tomimg/php/destruct.php5 Expected result: ---------------- Please see comments in file. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27903&edit=1
