Date: Mon, 23 Feb 2015 16:01:13 -0700 From: Friar Puck <p...@birchwood-abbey.net>
The condvar.scm file already serializes its operations, yet still uses without-interrupts, presumably for another reason. I am guessing that the intention is to stave off "aborts" or ANY keyboard interrupt that could eventually throw and leave globally accessible (by threads other than The Aborted One) data structures inconsistent. Correct. Same with, e.g., the WITHOUT-INTERRUPTS in hashtb.scm. Or without-keyboard-interrupts is just needlessly wordy and adds to the size of the SMP patches. In the end, without-interrupts can be changed to use with-thread-events-blocked, allowing thread switching where it will do no harm. Which to choose? It's not about threads per se, and it's not about the keyboard per se. If you want a name other than WITHOUT-INTERRUPTS for greppability's sake, how about WITHOUT-INTERRUPTION? _______________________________________________ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org https://lists.gnu.org/mailman/listinfo/mit-scheme-devel
