> From: Richard Kelsey <xxxxxx@s48.org>

    > Within the context of this SRFI I don't care about asynchronous
    > execution (I do care about threads, but as long as C code is not
    > interrupted asychronously they don't matter).  The GC protection
    > mechanism described in the SRFI is inadequate if GCs can occur
    > asynchronously.  Even if variables 'a' and 'b' are protected,
    > there is no guarentee that a = b; will not temporarily store the
    > value of 'b' in some unprotected location such as a register.

Ok, I don't care about this srfi anymore.

You've been presented simple solutions that eliminate those
limitations.  I don't think you have any good reason to blow them off
that way.

-t