Jörg F. Wittenberger wrote:
John is right about the general case. There are however circumstances
when you just want to abort some operation. If you know what you do,
external abort is sometimes ok. Most of the time however I'd
recommend to use thread-signal! to allow the terminated thread
Hi,
Does anyone know if thread-terminate! can safely be called on a
thread which is blocking on thread-wait-for-i/o!, without putting
chicken's internals into an inconsistent state. I have been doing so
without any noticeable adverse effects, but I wondered if this was just
because I have been
Chris Vine:
Does anyone know if thread-terminate! can safely be called on a
thread which is blocking on thread-wait-for-i/o!, without putting
chicken's internals into an inconsistent state.
Calling thread-terminate! in any circumstances may put your code
into a bad state, because it unlocks
Am 20.01.2015 um 23:41 schrieb co...@ccil.org:
Chris Vine:
Does anyone know if thread-terminate! can safely be called on a
thread which is blocking on thread-wait-for-i/o!, without putting
chicken's internals into an inconsistent state.
Calling thread-terminate! in any circumstances may
