Req #62919 [Com]: Serialize Reflection
Edit report at https://bugs.php.net/bug.php?id=62919&edit=1
ID: 62919
Comment by: tom at r dot je
Reported by: mattia dot citterio at gmail dot com
Summary: Serialize Reflection
Status: Open
Type: Feature/Change Request
Package: Reflection related
Operating System: Linux
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
This would be very useful, however I can see why this may be problematic for internals. If the class
definition has changed since the reflection object was serialized and unserialzed, then it would
cause all sorts of issues. The only sensible thing that __wakeup could do is call __construct, and
in actual fact, this works:
class A {
public function __construct() {
}
}
$r = new ReflectionClass('A');
$s = serialize($r);
$r1 = unserialize($s);
$r1->__construct('A');
$a = $r1->newInstanceArgs();
var_dump($a);
So having __wakeup call __construct with the class name would allow reflection to be serialized, if
like me, you were hoping to cache reflection using memcached for performance reasons, serialization
in this manner would not be beneficial as it would be just as slow to unserialize as to construct a
new object.
Previous Comments:
------------------------------------------------------------------------
[2012-08-24 09:32:03] laruence@php.net
Reflection* doesn't define their __sleep/__wakeup methods. so change to FR
instead of a bug
------------------------------------------------------------------------
[2012-08-24 09:26:19] mattia dot citterio at gmail dot com
Description:
------------
Cannot serialize/deserialize objects. This is the produced error on the last line:
PHP Fatal error: ReflectionClass::newInstanceArgs(): Internal error: Failed to
retrieve the reflection object
Test script:
---------------
class A {
public function __construct() {
}
}
$r = new ReflectionClass('A');
$r = unserialize(serialize($r));
$a = $r->newInstanceArgs(array());
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=62919&edit=1
Thread (4 messages)