This is the mail archive of the
guile@sources.redhat.com
mailing list for the Guile project.
Re: continuation and multi-threading
Keisuke Nishida <kxn30@po.cwru.edu> writes:
> > Hmm, this reminds me, if the local variables are kept on the stack,
> > and that stack is copied, set! won't stick after invoking a
> > continuation (contrary to R5RS). So you must keep local variables in
> > frames anyway.
>
> Hmm, right. I didn't think of it. I think I have to export all local
> variables within a closure that uses call/cc as external variables.
> This is not so hard, but very inefficient.
You may have problems with the upward closures. As I understand your
VM, it would restore -all- the local variables in -all- the stack
frames on stack copy.
The problem is that Scheme -really- relies on environments being a
tree.
--
How to eff the ineffable?