You need to avoid a race between two processes trying to modify the cell at the same time.
On Sat, Dec 19, 2009 at 10:49 PM, Taylor R Campbell <[email protected]> wrote: > (HASH-TABLE/MODIFY! <hash-table> <key> <modifier> [<default>]) may > call <modifier> with interrupts blocked, or with the same mask as in > the caller of HASH-TABLE/MODIFY!. I can't think of any reason to > block interrupts during the call to <modifier>, and it seems confusing > to me to call it in one of two very different states; does it seem > sensible to pull the call to it outside WITH-TABLE-LOCKED! in the body > of MAKE-METHOD:MODIFY!'s lambda in hashtb.scm? And if we made that > change, would it b necessary to lock the table at all (i.e., to block > interrupts) for the single write that SET-ENTRY-DATUM! incurs? > > > _______________________________________________ > MIT-Scheme-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/mit-scheme-devel > -- ~jrm _______________________________________________ MIT-Scheme-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/mit-scheme-devel
