From
http://www.eros-os.org/pipermail/e-lang/2004-June/009863.html
When an object's uncall target (x.__optUncall()[0]) is
itself part of
the serialized subgraph (which happens for any foreseen
facet),
unserialization *might* fail (depending on the order of
traversal of
the original object graph during serialization),
because the target may
be called before it is itself constructed.
I have avoided this problem for Den by using E.send/3
in uncalls, but
this has the consequence that the unserialized graph is
not in a usable
state until an indeterminate number of turns have passed.
I believe (with no evidence) that this workaround will
not be
sufficient for some applications. I also find it ugly.
Previous discussion:
http://www.eros-os.org/pipermail/e-lang/2003-December/009329.html
http://www.eros-os.org/pipermail/e-lang/2003-December/009349.html
http://www.eros-os.org/pipermail/e-lang/2003-December/009328.html
http://www.eros-os.org/pipermail/e-lang/2003-December/009327.html
