Btw, could you finally give me even a slight hint at how GC knows
that an object is not used anylonger?

  What you write sounds like it knows it by magic. Of course that can't
be, so there must be some other way. There must be *some* way for the
GC engine to know that in the code being currently executed there are
no references pointing to the objects. Assuming that the references
themselves don't tell the GC engine when they die (because that would
be reference counting!) then how? The GC has to also make a difference
between a reference being actually used in the currently-executed code
and an orphan reference.
  If object of type A has a reference to an object of the B, and the
latter also has a reference to the former, what does the GC engine do
to see that these are actually just orphan references? Does it follow
the references and see the recursion? What if there's a million objects
linked like this? Does it go through all of them? What happens if one
of the objects was still in use in the code? Was the traversal a waste
of time?

  I don't get it.

-- 
                                                          - Warp

Post a reply to this message