(2013/04/29 1:19), Magnus Holm wrote:
> In hindsight I think that the sliding views-technique is only required
> if you have multiple threads running at the same time. In CRuby there
> will only be a single thread running Ruby code so this becomes easier.
> For a concurrent tracer (tracing/marking objects as the Ruby thread
> runs) the most important thing is to get a consistent view of the heap.

Please read my previous message: "I don't think it is acceptable for
CRuby (because CRuby moves memory areas!)".

Concurrent tracing needs an assumption that "do not move (free) memory
area except sweeping timing". Current CRuby does.
For example: "ary << obj". Yes, the CRuby's memory management strategy
(assumption) is different from normal interpreters.

-- 
// SASADA Koichi at atdot dot net