Paul Brannan wrote:
> They restore the state of the stack, not the state of the heap.  This is
> the desired behavior.

right.

>> Further the use of continuations is limited to the thread they are
>> created in. This seems to be caused by implementing continuations with
>> threads.
> 
> Continuations are implemented with fibers on 1.9.

unright.

Fibers and Continuations are implemented by same way.  This does not
mean Conts are impled by Fibers.

> They still cannot be
> called across threads.  AFAIK changing this would be a huge undertaking,
> because saving the C stack in one thread and restoring it in another
> thread could result in objects being restored to a different place in
> memory than they were created, or even duplicated C objects on the stack
> that were not properly constructed/initialized.

maybe right.

-- 
// SASADA Koichi at atdot dot net