Re[2]: Questions on changing Chicken runtime and some other stuff

fw> > One has to distinguish between the initial garbage collector, which moves
fw> > nongarbage from the (garbage) stack to the heap, and garbage collections
fw> > within the heap.  The first is part of the Chicken way of doing business;
fw> > the second could probably be replaced by a different GCed heap, or even
fw> > a conservative GC such as Boehm-Demers-Weiser.
fw> >
fw> Yes, that would be exactly the way. All the stack-managing machinery
fw> makes still sense in such an environment. What would have to be modified
fw> is the write-barrier (C_mutate) and copying live stack data into the
fw> secondary heap (which in this case would be managed differently).
fw> Where I see problems, though are data-representation issues...

Could you please elaborate more on these issues? BTW what secondary GC strategy 
does Chicken use?