[GemStone-Smalltalk] objectForOop: question about some errors we get + how to implement a weak reference?

Otto Behrens otto at finworks.biz
Fri Jul 22 20:40:19 PDT 2022

> I agree, unless it is somehow re-attached. I think this is possible.
> Getting hold of an object that was marked as dead can somehow resurrect it,
> even if the gem that accessed it has the reference in transient memory.
> Perhaps this has something to do with it: there is a reference now (after
> looking at it) or the dead object was moved to a location meant for objects
> that are not dead.

This argument of mine was just silly because the _objectForOop: call throws
the exception.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/gemstone-smalltalk/attachments/20220723/792851bb/attachment-0001.htm>

More information about the GemStone-Smalltalk mailing list