[M3devel] WeakRef mechanism alive and well? cm3-cvshead

[Dragiša Durić]

(timezones, :)

On Fri, 2008-03-14 at 07:45 +0100, Dragiša Durić wrote:
...
> My understanding of conservativeness of GC with regard to register and
> stack content was something else... I was thinking it's like this:
> ProcessStacks will process registers and stacks; each time
> address-sized, correctly-aligned bit pattern which looks like address of
> some object GC knows occurs, GC accepts it as it's address - it maybe is
> not, but conservative thinking will not make risks there. This way,
> ProcessStacks will know exactly what objects are (maybe, but no
> risks...) referenced from stack. 
> 
> I know I am missing something here, and that's why I ask, why don't you
> do it just like this?

I saw why... And I think I have some ideas here. When I finish reading
your RTCollector.m3 I'll come back to this subject.

-- 
Dragiša Durić <dragisha at m3w.org>