>
>Whether it is specified in this SRFI or another one, the exit
>procedure can either unwind the dynamic-wind stack or not:

>
>[...]

Your suggestions about "exit" are certainly very true, but as you correctly
point out, the semantic issues of a "standard" "exit" are rather unclear,
and IMHO it would be better to leave it out alltogether.
Defining your own "exit" is trivial, and if the user makes use of "dynamic-wind",
the she should be aware of the consequences and write her code (and her
unwinding thunks) carefully (she has to do it anyway).
Moving the responsibility to SRFI-22 makes it unnecessarily complicated,
for very little gain.

cheers,
felix