1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-04-30 11:50:28 +02:00

doc: #:autoload does not pull in all the module bindings.

Reported by Jan Nieuwenhuizen <janneke@gnu.org>.
This is a followup to cb14fd2143.

* doc/ref/api-modules.texi (Creating Guile Modules): Remove bit that
says all the bindings of an autoloaded module become available.
This commit is contained in:
Ludovic Courtès 2020-05-22 22:06:34 +02:00
parent ac5df66f1c
commit 723e483e7d

View file

@ -1,6 +1,6 @@
@c -*-texinfo-*-
@c This is part of the GNU Guile Reference Manual.
@c Copyright (C) 1996, 1997, 2000-2004, 2007-2014, 2019
@c Copyright (C) 1996, 1997, 2000-2004, 2007-2014, 2019, 2020
@c Free Software Foundation, Inc.
@c See the file guile.texi for copying conditions.
@ -295,8 +295,10 @@ example,
(set! foo (delete-duplicates ...)))
@end example
When a module is autoloaded, all its bindings become available.
@var{symbol-list} is just those that will first trigger the load.
When a module is autoloaded, only the bindings in @var{symbol-list}
become available@footnote{In Guile 2.2 and earlier, @emph{all} the
module bindings would become available; @var{symbol-list} was just the
list of bindings that will first trigger the load.}.
An autoload is a good way to put off loading a big module until it's
really needed, for instance for faster startup or if it will only be