diff options
author | Andy Wingo <wingo@pobox.com> | 2017-05-22 14:13:20 +0200 |
---|---|---|
committer | Andy Wingo <wingo@pobox.com> | 2017-05-22 14:15:40 +0200 |
commit | b2c0e01bb48bea1876e8cb26e0f5ffac17069e9d (patch) | |
tree | a34015792dd34377e5898037c46128c8546c9939 /doc/ref/libguile-foreign-objects.texi | |
parent | c248ea10beb2afa4c113dbc6dc707bed5dbfc92e (diff) | |
download | guile-b2c0e01bb48bea1876e8cb26e0f5ffac17069e9d.tar.gz |
Update effective version to 3.0
* GUILE-VERSION: Bump version to 2.3.0, and effective version to 3.0.
* .gitignore:
* README:
* doc/guile.1:
* doc/ref/api-evaluation.texi:
* doc/ref/api-options.texi:
* doc/ref/guile-invoke.texi:
* doc/ref/libguile-foreign-objects.texi:
* doc/ref/libguile-parallel.texi:
* doc/ref/srfi-modules.texi: Update to 3.0.
* libguile/_scm.h (SCM_OBJCODE_MAJOR_VERSION):
(SCM_OBJCODE_MINIMUM_MINOR_VERSION, SCM_OBJCODE_MINOR_VERSION): Bump
bytecode version for fallback path.
* libguile/loader.c: Update to avoid loading version 2.2 bytecode
files.
* meta/guile-3.0-uninstalled.pc.in:
* meta/guile-3.0.pc.in: Rename.
* module/system/vm/assembler.scm (*bytecode-major-version*):
(*bytecode-minor-version*): Write the new bytecode version.
Diffstat (limited to 'doc/ref/libguile-foreign-objects.texi')
-rw-r--r-- | doc/ref/libguile-foreign-objects.texi | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/doc/ref/libguile-foreign-objects.texi b/doc/ref/libguile-foreign-objects.texi index 29e1f8619..0603496d0 100644 --- a/doc/ref/libguile-foreign-objects.texi +++ b/doc/ref/libguile-foreign-objects.texi @@ -276,13 +276,11 @@ make_file (int fd) @cindex finalization Note that the finalizer may be invoked in ways and at times you might -not expect. In particular, if the user's Guile is built with support -for threads, the finalizer may be called from any thread that is running -Guile. In Guile 2.0, finalizers are invoked via ``asyncs'', which -interleaves them with running Scheme code; @pxref{Asyncs}. In Guile 2.2 -there will be a dedicated finalization thread, to ensure that the -finalization doesn't run within the critical section of any other thread -known to Guile. +not expect. In a Guile built without threading support, finalizers are +invoked via ``asyncs'', which interleaves them with running Scheme code; +@pxref{Asyncs}. If the user's Guile is built with support for threads, +the finalizer will probably be called by a dedicated finalization +thread, unless the user invokes @code{scm_run_finalizers ()} explicitly. In either case, finalizers run concurrently with the main program, and so they need to be async-safe and thread-safe. If for some reason this |