85 lines
3.5 KiB
HTML
85 lines
3.5 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html>
|
||
|
|
<!-- Created by GNU Texinfo 7.1, https://www.gnu.org/software/texinfo/ -->
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<!-- This manual documents Guile version 3.0.10.
|
||
|
|
|
||
|
|
Copyright (C) 1996-1997, 2000-2005, 2009-2023 Free Software Foundation,
|
||
|
|
Inc.
|
||
|
|
|
||
|
|
Copyright (C) 2021 Maxime Devos
|
||
|
|
|
||
|
|
Copyright (C) 2024 Tomas Volf
|
||
|
|
|
||
|
|
|
||
|
|
Permission is granted to copy, distribute and/or modify this document
|
||
|
|
under the terms of the GNU Free Documentation License, Version 1.3 or
|
||
|
|
any later version published by the Free Software Foundation; with no
|
||
|
|
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
|
||
|
|
copy of the license is included in the section entitled "GNU Free
|
||
|
|
Documentation License." -->
|
||
|
|
<title>Deprecation (Guile Reference Manual)</title>
|
||
|
|
|
||
|
|
<meta name="description" content="Deprecation (Guile Reference Manual)">
|
||
|
|
<meta name="keywords" content="Deprecation (Guile Reference Manual)">
|
||
|
|
<meta name="resource-type" content="document">
|
||
|
|
<meta name="distribution" content="global">
|
||
|
|
<meta name="Generator" content=".texi2any-real">
|
||
|
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||
|
|
|
||
|
|
<link href="index.html" rel="start" title="Top">
|
||
|
|
<link href="Concept-Index.html" rel="index" title="Concept Index">
|
||
|
|
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
|
||
|
|
<link href="API-Reference.html" rel="up" title="API Reference">
|
||
|
|
<link href="The-SCM-Type.html" rel="next" title="The SCM Type">
|
||
|
|
<link href="API-Overview.html" rel="prev" title="API Overview">
|
||
|
|
<style type="text/css">
|
||
|
|
<!--
|
||
|
|
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
|
||
|
|
span:hover a.copiable-link {visibility: visible}
|
||
|
|
-->
|
||
|
|
</style>
|
||
|
|
<link rel="stylesheet" type="text/css" href="https://www.gnu.org/software/gnulib/manual.css">
|
||
|
|
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body lang="en">
|
||
|
|
<div class="section-level-extent" id="Deprecation">
|
||
|
|
<div class="nav-panel">
|
||
|
|
<p>
|
||
|
|
Next: <a href="The-SCM-Type.html" accesskey="n" rel="next">The SCM Type</a>, Previous: <a href="API-Overview.html" accesskey="p" rel="prev">Overview of the Guile API</a>, Up: <a href="API-Reference.html" accesskey="u" rel="up">API Reference</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
|
||
|
|
</div>
|
||
|
|
<hr>
|
||
|
|
<h3 class="section" id="Deprecation-1"><span>6.2 Deprecation<a class="copiable-link" href="#Deprecation-1"> ¶</a></span></h3>
|
||
|
|
|
||
|
|
<p>From time to time functions and other features of Guile become obsolete.
|
||
|
|
Guile’s <em class="dfn">deprecation</em> is a mechanism that can help you cope with
|
||
|
|
this.
|
||
|
|
</p>
|
||
|
|
<p>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 class="code">libguile</code> will cause a link-time warning.
|
||
|
|
</p>
|
||
|
|
<p>The primary source for information about just what interfaces are
|
||
|
|
deprecated in a given release is the file <samp class="file">NEWS</samp>. That file also
|
||
|
|
documents what you should use instead of the obsoleted things.
|
||
|
|
</p>
|
||
|
|
<p>The file <samp class="file">README</samp> 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.
|
||
|
|
</p>
|
||
|
|
<p>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.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|