diff options
| author | Marius Vollmer <mvo@zagadka.de> | 2005-12-06 20:27:59 +0000 |
|---|---|---|
| committer | Marius Vollmer <mvo@zagadka.de> | 2005-12-06 20:27:59 +0000 |
| commit | 54428bb84e2f212d6c24ef5264780d88fd31da60 (patch) | |
| tree | 5f1acf0d1532178e3bc7b7228d177fce11b7bb3b /doc/ref/libguile-concepts.texi | |
| parent | b54df25486b29f4759b71d3c1af51010e26fc2f3 (diff) | |
| download | guile-54428bb84e2f212d6c24ef5264780d88fd31da60.tar.gz | |
Removed scm_leave_guile, scm_enter_guile and all references to
them since they are no longer in the API.
Diffstat (limited to 'doc/ref/libguile-concepts.texi')
| -rw-r--r-- | doc/ref/libguile-concepts.texi | 21 |
1 files changed, 10 insertions, 11 deletions
diff --git a/doc/ref/libguile-concepts.texi b/doc/ref/libguile-concepts.texi index dca61058f..c969bdaa9 100644 --- a/doc/ref/libguile-concepts.texi +++ b/doc/ref/libguile-concepts.texi @@ -451,17 +451,16 @@ that are stored in local variables. When a thread puts itself into guile mode for the first time, it gets a Scheme representation and is listed by @code{all-threads}, for example. -While in guile mode, a thread promises to reach a safe point reasonably -frequently (@pxref{Asynchronous Signals}). In addition to running -signal handlers, these points are also potential rendezvous points of -all guile mode threads where Guile can orchestrate global things like -garbage collection. Consequently, when a thread in guile mode blocks -and does no longer frequent safe points, it might cause all other guile -mode threads to block as well. To prevent this from happening, a guile -mode thread should either only block in libguile functions (who know how -to do it right), or should temporarily leave guile mode with -@code{scm_without_guile} or -@code{scm_leave_guile}/@code{scm_enter_guile}. +While in guile mode, a thread promises to reach a safe point +reasonably frequently (@pxref{Asynchronous Signals}). In addition to +running signal handlers, these points are also potential rendezvous +points of all guile mode threads where Guile can orchestrate global +things like garbage collection. Consequently, when a thread in guile +mode blocks and does no longer frequent safe points, it might cause +all other guile mode threads to block as well. To prevent this from +happening, a guile mode thread should either only block in libguile +functions (who know how to do it right), or should temporarily leave +guile mode with @code{scm_without_guile}. For some common blocking operations, Guile provides convenience functions. For example, if you want to lock a pthread mutex while in |