#36487 [Opn->Bgs]: object === same object mismatch

ID: 36487 Updated by: auroraeosrose@php.net Reported By: xxoes at nw7 dot de -Status: Open +Status: Bogus Bug Type: PHP-GTK related Operating System: * PHP Version: 5.1.2 New Comment: The order that objects are destroyed in cannot be guaranteed, so it's generally a good idea not to be trying to fiddle with objects (even objects stored inside other objects) in destructors Previous Comments: ------------------------------------------------------------------------ [2006-03-28 14:14:10] xxoes at nw7 dot de No isn't php-gtk related. Is a general problem because DOMElement and GtkObject have the same result. ------------------------------------------------------------------------ [2006-03-28 12:55:19] mike@php.net So this is GTK related then, isn't it? ------------------------------------------------------------------------ [2006-02-23 10:16:37] cweiske@php.net As far as I see that, the objects *are* identical. They equal === as long as they are not in the process of being destroyed - but as soon as the destroying process is begun, they don't equal any more although they are still equal ------------------------------------------------------------------------ [2006-02-23 08:05:56] xxoes at nw7 dot de Sorry but i don't understand! Thats are the same objects and the same instances, and === doesn't matched! It works fine if a call $obj->__destruct === is true, but not if this function is called by php on exit. ------------------------------------------------------------------------ [2006-02-22 16:42:39] iliaa@php.net 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 For === to return true on object comparison both objects must be instances of the same class and refer to the exact same internal object. ------------------------------------------------------------------------ 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/36487 -- Edit this bug report at http://bugs.php.net/?id=36487&edit=1