Hi,

At Mon, 21 Sep 2009 16:26:17 +0900,
Suraj Kurapati wrote in [ruby-core:25691]:
> > I don't think it's guaranteed to resume a fiber in different
> > rb_protect scope.
> 
> Why is that?  Does each rb_protect scope have a different
> running thread (with a different stack + heap)?  Is there
> danger of a cross-thread violation?

Maybe safe, maybe dangerous, noone has confirmed, nor
considered it yet.  There is no cross-thread violation like
checks right now, but it might be figured out that the check is
necessary.

> Should I try to store the original rb_protect scope into a
> variable and reuse it when resuming my Fiber?  What do you
> suggest?

Create a new thread and use fibers within one rb_protect.

-- 
Nobu Nakada