Abdulaziz Ghuloum <aghuloum_at_cs.indiana.edu> writes:
> [Lots of explanation]
> Basically, in your model, you lose side effects when you exit the
> dynamic context, while in Kent's model, side effects to parameters
> are remembered and restored properly.
So the swapping compensates for the effect of side effects, and gets a
notion similar to "call/cc captures the contents of the storage
associated with the parameters." Except it seems to break down in the
presence of threads, as Kent explained here:
http://lists.r6rs.org/pipermail/r6rs-discuss/2007-February/001536.html
Now, everything I know about the issue indicates that fracture points
like this are inherent in the use of thread-local storage, and no
amount of compensation can get back the simple semantics back.
--
Cheers =8-} Mike
Friede, V?lkerverst?ndigung und ?berhaupt blabla
Received on Wed Feb 21 2007 - 05:30:05 UTC