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 mutexes without letting the user data structures that those mutexes protect be unwound. In general, terminating threads from outside is always a Bad Thing. -- John Cowan http://www.ccil.org/~cowan [email protected] Kill Gorgun! Kill orc-folk! No other words please Wild Men. Drive away bad air and darkness with bright iron! --Ghan-buri-Ghan _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
