> I'm not doing any call/cc or non-local exit shenanigans, but the code > uses srfi-18 threads and does I/O over TCP. As I understand it, srfi-18 > is implemented using continuations. Will that cause problems with my > with-lock function? I'm thinking that a thread that has aquired the lock > in the before-thunk and running the main thunk might hang waiting for > I/O; will that cause it to exit the dynamic environment, run the > after-thunk and release the lock?
Each thread has its own dynamic-wind chain, so unless you start threads in the before/after threads, you should be fine. felix
