#24670 [NoF->Bgs]: defining __call requires __sleep for serialize/session

From: Date: Mon, 30 May 2005 08:04:39 +0000
Subject: #24670 [NoF->Bgs]: defining __call requires __sleep for serialize/session
References: 1  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969368361@lists.php.net to get a copy of this message
ID: 24670 Updated by: lsmith@php.net Reported By: tater at potatoe dot com -Status: No Feedback +Status: Bogus Bug Type: Documentation problem Operating System: OS X 10.2 PHP Version: Irrelevant Assigned To: dmitry New Comment: dupes are marked as bogus, and #30791 seems to be more detailed. Previous Comments: ------------------------------------------------------------------------ [2005-05-30 10:02:29] lsmith@php.net this seems to be a dupe of #30791 ------------------------------------------------------------------------ [2005-04-22 01:00:03] phpdoc 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-04-14 10:23:31] vrana@php.net It seems that classes with __call or __sleep (!) methods simply can't be serialized (serialize() returns "N;" for them). If you can reproduce it, please change the Category of this bug to Zend Engine 2 problem. And fill in your PHP Version, please. ------------------------------------------------------------------------ [2005-04-01 13:52:48] maka3d at yahoo dot com dot br Does there is a workaround to this? I did some tests but didn't work? I thought it would be fixed until 5.0.4 ------------------------------------------------------------------------ [2004-05-17 23:28:58] magicking89 at hotmail dot com I have the same problem with PHP5 RC2 on Mac Os X 10.2 It's a real problem because I must to close socket with __sleep but it doesn't work correctly... ------------------------------------------------------------------------ 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/24670 -- Edit this bug report at http://bugs.php.net/?id=24670&edit=1

« previous php.doc (#969368361) next »