#30791 [NoF->Ver]: overload and serialize produce unexpected behaviour

ID: 30791 Updated by: alan_k@php.net Reported By: alan at akbkhome dot com -Status: No Feedback +Status: Verified Bug Type: Zend Engine 2 problem Operating System: * PHP Version: 5CVS-2004-11-15 (dev) New Comment: This bug needs either fixing or verifying as wont-fix. (or documenting....) so leaving it as verified until one of those occur... Previous Comments: ------------------------------------------------------------------------ [2005-03-15 01:00:34] 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". ------------------------------------------------------------------------ [2005-03-07 21:55:43] sniper@php.net This is what I get with latest CVS HEAD: # php5 t.php Notice: serialize(): __sleep should return an array only containing the names of instance-variables to serialize. in /home/jani/t.php on line 10 ------------------------------------------------------------------------ [2005-01-13 02:13:41] alan_k@php.net Changing to verified - although it's not critical (as overload was experimental in 4.x) it is a BC break - and is a relatively unexpected behaviour.. ------------------------------------------------------------------------ [2005-01-13 02:10:25] alan at akbkhome dot com Marcus already confirmed this needs fixing - the serialize code should not end up calling __call() on overloaded objects. ------------------------------------------------------------------------ [2005-01-13 00:02:03] tony2001@php.net >If an object is overloaded (with __call()), then >serializ'ing the object will fail unless __sleep() is defined. .. or unless __call() returns Array of instance names. I'd say there is no bug, 'cos your overloaded __sleep() method indeed returns wrong data. ------------------------------------------------------------------------ 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/30791 -- Edit this bug report at http://bugs.php.net/?id=30791&edit=1