1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-12 06:41:13 +02:00

Couple cleanups.

This commit is contained in:
Marius Vollmer 2005-03-09 22:09:11 +00:00
parent 99ec43c198
commit a6d75e533e

38
NEWS
View file

@ -63,8 +63,8 @@ the GC.
The default is "pthreads", unless your platform doesn't have pthreads, The default is "pthreads", unless your platform doesn't have pthreads,
in which case "null" threads are used. in which case "null" threads are used.
See the manual for details, nodes "Initialization", "Multi-Threading" See the manual for details, nodes "Initialization", "Multi-Threading",
and "Blocking". "Blocking", and others.
** There is the new notion of 'discouraged' features. ** There is the new notion of 'discouraged' features.
@ -968,7 +968,12 @@ This function calls 'free' on a given pointer when a frame is left.
Thus the call to scm_frame_unwind_handler above could be replaced with Thus the call to scm_frame_unwind_handler above could be replaced with
simply scm_frame_free (mem). simply scm_frame_free (mem).
** New way to block and unblock asyncs ** New functions scm_c_call_with_blocked_asyncs and
scm_c_call_with_unblocked_asyncs
Like scm_call_with_blocked_asyncs etc. but for C functions.
** New functions scm_frame_block_asyncs and scm_frame_unblock_asyncs
In addition to scm_c_call_with_blocked_asyncs you can now also use In addition to scm_c_call_with_blocked_asyncs you can now also use
scm_frame_block_asyncs in a 'frame' (see above). Likewise for scm_frame_block_asyncs in a 'frame' (see above). Likewise for
@ -980,7 +985,13 @@ scm_c_call_with_unblocked_asyncs and scm_frame_unblock_asyncs.
They do no longer fulfill their original role of blocking signal They do no longer fulfill their original role of blocking signal
delivery. Depending on what you want to achieve, replace a pair of delivery. Depending on what you want to achieve, replace a pair of
SCM_DEFER_INTS and SCM_ALLOW_INTS with a frame that locks a mutex, SCM_DEFER_INTS and SCM_ALLOW_INTS with a frame that locks a mutex,
blocks asyncs, or both. blocks asyncs, or both. See node "Critical Sections" in the manual.
** The value 'scm_mask_ints' is no longer writable.
Previously, you could set scm_mask_ints directly. This is no longer
possible. Use scm_c_call_with_blocked_asyncs and
scm_c_call_with_unblocked_asyncs instead.
** New way to temporarily set the current input, output or error ports ** New way to temporarily set the current input, output or error ports
@ -1054,17 +1065,6 @@ arguments are now passed directly:
This is an incompatible change. This is an incompatible change.
** The value 'scm_mask_ints' is no longer writable.
Previously, you could set scm_mask_ints directly. This is no longer
possible. Use scm_c_call_with_blocked_asyncs and
scm_c_call_with_unblocked_asyncs instead.
** New functions scm_c_call_with_blocked_asyncs and
scm_c_call_with_unblocked_asyncs
Like scm_call_with_blocked_asyncs etc. but for C functions.
** New snarfer macro SCM_DEFINE_PUBLIC. ** New snarfer macro SCM_DEFINE_PUBLIC.
This is like SCM_DEFINE, but also calls scm_c_export for the defined This is like SCM_DEFINE, but also calls scm_c_export for the defined
@ -1173,14 +1173,6 @@ function as the callback instead of a SCM value.
Use scm_std_select, scm_std_sleep, scm_std_usleep instead. Use scm_std_select, scm_std_sleep, scm_std_usleep instead.
** SCM_DEFER_INTS and SCM_ALLOW_INTS have been deprecated.
Use, for example, scm_frame_critical_section to mark critical
sections.
SCM_REDEFER_INTS and SCM_REALLOW_INTS are deprecated as well, of
course.
** Many definitions have been removed that were previously deprecated. ** Many definitions have been removed that were previously deprecated.
scm_lisp_nil, scm_lisp_t, s_nil_ify, scm_m_nil_ify, s_t_ify, scm_lisp_nil, scm_lisp_t, s_nil_ify, scm_m_nil_ify, s_t_ify,