On 2004/07/01, at 14:25, Andi Gutmans wrote:
Hi Moriyoshi,
The object handle is not a unique identifier. Different object types
(e.g. PHP objects, SimpleXML objects) can have the same object handle.
The real unique identifier is object handle + object handlers array or
more useful in your case,
this would still not suffice for a proper serialization, overloaded
objects should have serialize and unserialize handlers something
for 5.1 methinks.
-sterling
On Thu, 1 Jul 2004 16:03:09 +0900, Moriyoshi Koizumi
[EMAIL PROTECTED] wrote:
On 2004/07/01, at 14:25, Andi Gutmans wrote:
This is the new one. Hope it is ready to commit this time.
http://www.voltex.jp/patches/bug28325-preliminary-20040701.patch.diff
Two untidy bitshifts are intended to form an atomic bit rotation and
are somewhat necessary for the uniqueness of the hash value.
At least 31 object handles of the same
Andi Gutmans wrote:
The object handle is not a unique identifier.
Are there any plans on implementing a really unique identifier to
objects? This would, among other things, allow objects to be used as
array keys.
--
Sebastian Bergmann
http://sebastian-bergmann.de/
Hello Sterling,
i have that on my personal 5.1 todo list since months...
marcus
Thursday, July 1, 2004, 6:29:53 PM, you wrote:
this would still not suffice for a proper serialization, overloaded
objects should have serialize and unserialize handlers something
for 5.1 methinks.
Hi Moriyoshi,
The object handle is not a unique identifier. Different object types (e.g.
PHP objects, SimpleXML objects) can have the same object handle. The real
unique identifier is object handle + object handlers array or more useful
in your case, possibly class name and object handle.
Andi
