[r6rs-discuss] [Formal] SRFI-39 should be made an R6RS library
R. Kent Dybvig
dyb at cs.indiana.edu
Sun Feb 11 12:40:56 EST 2007
> That's a strange way to interpret "separate," since both mechanisms
> are joined with parameters. Why aren't dynamic binding and
> thread-local storage separate?
Hmm. I guess any mechanism that allows per-thread locations to be
dynamically bound would be considered a combined mechanism by your
definition. Are you suggesting that one should not dynamically bind
per-thread locations? I can't myself imagine wanting to dynamically bind
locations that aren't per thread.
> Our Scheme workshop spells out exactly
> what the semantic problems are. (Specifically, they occur when a
> escape procedure created in one thread is invoked in another.)
Again, I don't believe that there is a problem. Parameterize, like
fluid-let, just assigns a new value on entry and restores the old on exit,
and the semantics wrt thread-local paramters, even if the assignment is
performed by a continuation created in another thread, is totally well
defined.
Kent
More information about the r6rs-discuss
mailing list