[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] master c78f872 2/2: Clarify thread-signal semantics
From: |
Noam Postavsky |
Subject: |
[Emacs-diffs] master c78f872 2/2: Clarify thread-signal semantics |
Date: |
Tue, 13 Dec 2016 02:45:42 +0000 (UTC) |
branch: master
commit c78f872a5667abacb3531edd9aad969af31a3e1f
Author: Noam Postavsky <address@hidden>
Commit: Noam Postavsky <address@hidden>
Clarify thread-signal semantics
* doc/lispref/threads.texi (Basic Thread Functions): Explain that the
thread will be signaled as soon as possible.
---
doc/lispref/threads.texi | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/lispref/threads.texi b/doc/lispref/threads.texi
index 7ecfb19..de1c27b 100644
--- a/doc/lispref/threads.texi
+++ b/doc/lispref/threads.texi
@@ -82,9 +82,11 @@ immediately.
@defun thread-signal thread error-symbol data
Like @code{signal} (@pxref{Signaling Errors}), but the signal is
delivered in the thread @var{thread}. If @var{thread} is the current
-thread, then this just calls @code{signal} immediately.
address@hidden will cause a thread to exit a call to
address@hidden, @code{condition-wait}, or @code{thread-join}.
+thread, then this just calls @code{signal} immediately. Otherwise,
address@hidden will receive the signal as soon as it becomes current.
+If @var{thread} was blocked by a call to @code{mutex-lock},
address@hidden, or @code{thread-join}; @code{thread-signal}
+will unblock it.
@end defun
@defun thread-yield