* doc monitor
@ 2004-01-17 13:45 Kevin Ryde
0 siblings, 0 replies; only message in thread
From: Kevin Ryde @ 2004-01-17 13:45 UTC (permalink / raw)
* scheme-scheduling.texi (Higher level thread procedures): In monitor,
don't let "newly created" suggest a mutex created on every evaluation.
Note what "monitor" means.
- macro: monitor body...
Evaluate BODY, with a mutex locked so only one thread can execute
that code at any one time. Each `monitor' form has its own
private mutex and the locking is done per `with-mutex' above. The
return value is the return from the last form in BODY.
The term "monitor" comes from operating system theory, where it
means a particular bit of code managing access to some resource and
which only ever executes on behalf one one process at any one time.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-01-17 13:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-17 13:45 doc monitor Kevin Ryde
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).