diff options
author | Andy Wingo <wingo@pobox.com> | 2016-11-21 18:34:41 +0100 |
---|---|---|
committer | Andy Wingo <wingo@pobox.com> | 2016-11-21 18:35:08 +0100 |
commit | f927c70d4280a9644b9997108d67da2addb3eb65 (patch) | |
tree | 01367f147241b9a7430352fef08a8ed0b4a5c3ce /NEWS | |
parent | 1e925119969ea58396c79ab8e6c6c0130471eb22 (diff) |
Update join-thread docs
* doc/ref/api-scheduling.texi (Threads): Joining a foreign thread is an
error.
* NEWS: Update.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 9 |
1 files changed, 8 insertions, 1 deletions
@@ -54,7 +54,7 @@ deprecated; use `scm_timed_lock_mutex' instead. It used to be that `unlock-mutex' included `wait-condition-variable' functionality. This has been deprecated; use SRFI-18 if you want this -behavior from `mutex-unlock!'. Relatedly, `scm_unlock_mutex_timed is +behavior from `mutex-unlock!'. Relatedly, `scm_unlock_mutex_timed' is deprecated; use `scm_unlock_mutex' instead. ** Removed `unchecked-unlock' mutex flag @@ -73,6 +73,13 @@ The `set-thread-cleanup!' and `thread-cleanup' functions that were added in Guile 2.0 to support cleanup after thread cancellation are no longer needed, since threads can declare cleanup handlers via `dynamic-wind'. +** Only threads created by Guile are joinable + +`join-thread' used to work on "foreign" threads that were not created by +Guile itself, though their join value was always `#f'. This is no +longer the case; attempting to join a foreign thread will throw an +error. + * New deprecations ** Arbiters deprecated |