mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-04-30 03:40:34 +02:00
7545ddd42a
* doc/ref/api-control.texi (Handling Errors): Update docs for display-error. * libguile/backtrace.h (scm_i_display_error): Change prototype to s/stack/frame/. * libguile/throw.c (handler_message): Change invocation of scm_i_display_error to pass a frame. * doc/ref/api-deprecated.texi (Deprecation): Update wording. * doc/ref/api-evaluation.texi (Local Evaluation): Remove section on local-eval. * doc/ref/api-macros.texi: Fix a couple typos. * doc/ref/api-memory.texi (Objects): Remove terrible section. * doc/ref/api-procedures.texi (Procedure Properties): Remove docs for closure?. (Compiled Procedures): Update wording. * doc/ref/guile.texi (API Reference): Remove reference to "Objects".
29 lines
1.2 KiB
Text
29 lines
1.2 KiB
Text
@c -*-texinfo-*-
|
|
@c This is part of the GNU Guile Reference Manual.
|
|
@c Copyright (C) 1996, 1997, 2000, 2001, 2002, 2003, 2004, 2010
|
|
@c Free Software Foundation, Inc.
|
|
@c See the file guile.texi for copying conditions.
|
|
|
|
@node Deprecation
|
|
@section Deprecation
|
|
|
|
From time to time functions and other features of Guile become obsolete.
|
|
Guile's @dfn{deprecation} is a mechanism that can help you cope with
|
|
this.
|
|
|
|
When you use a feature that is deprecated, you will likely get a warning
|
|
message at run-time. Also, if you have a new enough toolchain, using a
|
|
deprecated function from @code{libguile} will cause a link-time warning.
|
|
|
|
The primary source for information about just what interfaces are
|
|
deprecated in a given release is the file @file{NEWS}. That file also
|
|
documents what you should use instead of the obsoleted things.
|
|
|
|
The file @file{README} contains instructions on how to control the
|
|
inclusion or removal of the deprecated features from the public API of
|
|
Guile, and how to control the deprecation warning messages.
|
|
|
|
The idea behind this mechanism is that normally all deprecated
|
|
interfaces are available, but you get feedback when compiling and
|
|
running code that uses them, so that you can migrate to the newer APIs
|
|
at your leisure.
|