Edit report at https://bugs.php.net/bug.php?id=55801&edit=1
ID: 55801 Comment by: mapi at pdepend dot org Reported by: mapi at pdepend dot org Summary: Behavior of unserialize has changed Status: Feedback Type: Bug Package: Variables related Operating System: Linux (Fedora 15) PHP Version: 5.4.0beta1 Assigned To: mike Block user comment: N Private report: N New Comment: Hello Mike, I just tested a patched version of "branches/PHP_5_4/" and "trunk/" with the original implementation that uses serialize() and unserialize() within __sleep()/__wakeup(). Everything works as expected and there are no NULL filled arrays anymore. Thank you very much for help Previous Comments: ------------------------------------------------------------------------ [2011-10-19 08:15:02] m...@php.net So? Running your original test script seems to work fine with this patch... ------------------------------------------------------------------------ [2011-10-13 16:21:18] m...@php.net The following patch has been added/updated: Patch Name: fix-serialize-in-sleep-and-wakeup Revision: 1318522878 URL: https://bugs.php.net/patch-display.php?bug=55801&patch=fix-serialize-in-sleep-and-wakeup&revision=1318522878 ------------------------------------------------------------------------ [2011-10-13 14:39:40] m...@php.net Could you try attached patch, please? ------------------------------------------------------------------------ [2011-10-13 14:39:10] m...@php.net The following patch has been added/updated: Patch Name: fix-serialize-in-sleep-and-wakeup Revision: 1318516750 URL: https://bugs.php.net/patch-display.php?bug=55801&patch=fix-serialize-in-sleep-and-wakeup&revision=1318516750 ------------------------------------------------------------------------ [2011-10-04 16:34:49] mapi at pdepend dot org To answer your question, I did't know my initial intention about the __temp__ property, but I remember that there was a reason. But it seems that this property is obsolete now. ------------------------------------------------------------------------ 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=55801 -- Edit this bug report at https://bugs.php.net/bug.php?id=55801&edit=1
