From: Lyle Johnson <ljohnson@...>
Date: 2001-02-23T23:40:03+09:00
Subject: [ruby-talk:11380] Re: Any way to control order in which objects are GC'd?

> Well as you see, gc and reference counting are not friends.
>
> So 3 suggestions.
>
> The first is to stop using reference counting.  (As already
> suggested by Dave.)

Dave & Ben,

Thanks very much for the discussion of the issues here. Actually, if I
understand the concept of reference counting, my problem is that the
underlying C++ library *doesn't* use reference counting! But at any rate, I
think the correct solution is going to be some modifications to the
underlying C++ library so that when one of these mutually dependent objects
get destroyed, the other one gets notified (so that it properly "forgets"
its reference). That way, the order in which Ruby's GC destroys the objects
won't matter anymore.

Thanks again,

Lyle