1
0
Fork 0
cl-sites/guile.html_node/provide-and-require.html

89 lines
3.4 KiB
HTML
Raw Normal View History

2024-12-17 12:49:28 +01:00
<!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>provide and require (Guile Reference Manual)</title>
<meta name="description" content="provide and require (Guile Reference Manual)">
<meta name="keywords" content="provide and require (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="Modules.html" rel="up" title="Modules">
<link href="Environments.html" rel="next" title="Environments">
<link href="Accessing-Modules-from-C.html" rel="prev" title="Accessing Modules from C">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
div.example {margin-left: 3.2em}
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="subsection-level-extent" id="provide-and-require">
<div class="nav-panel">
<p>
Next: <a href="Environments.html" accesskey="n" rel="next">Environments</a>, Previous: <a href="Accessing-Modules-from-C.html" accesskey="p" rel="prev">Accessing Modules from C</a>, Up: <a href="Modules.html" accesskey="u" rel="up">Modules</a> &nbsp; [<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>
<h4 class="subsection" id="provide-and-require-1"><span>6.18.11 provide and require<a class="copiable-link" href="#provide-and-require-1"> &para;</a></span></h4>
<p>Aubrey Jaffer, mostly to support his portable Scheme library SLIB,
implemented a provide/require mechanism for many Scheme implementations.
Library files in SLIB <em class="emph">provide</em> a feature, and when user programs
<em class="emph">require</em> that feature, the library file is loaded in.
</p>
<p>For example, the file <samp class="file">random.scm</samp> in the SLIB package contains the
line
</p>
<div class="example lisp">
<pre class="lisp-preformatted">(provide 'random)
</pre></div>
<p>so to use its procedures, a user would type
</p>
<div class="example lisp">
<pre class="lisp-preformatted">(require 'random)
</pre></div>
<p>and they would magically become available, <em class="emph">but still have the same
names!</em> So this method is nice, but not as good as a full-featured
module system.
</p>
<p>When SLIB is used with Guile, provide and require can be used to access
its facilities.
</p>
</div>
</body>
</html>