From: Tomas Volf <~@wolfsden.cz>
To: 71800@debbugs.gnu.org
Cc: Tomas Volf <~@wolfsden.cz>
Subject: bug#71800: [PATCH 2/2] doc: Fix implication of omitting optional arguments.
Date: Thu, 27 Jun 2024 16:18:52 +0200 [thread overview]
Message-ID: <20240627141852.30845-2-~@wolfsden.cz> (raw)
In-Reply-To: <20240627141852.30845-1-~@wolfsden.cz>
According to the previous wording, omitting all optional arguments led
to empty interface. That however was not the case and was only a
documentation bug (as confirmed by wingo on IRC). So let us fix that.
* doc/ref/api-modules.texi (Using Guile Modules): Fix implication of
omitting optional arguments.
---
doc/ref/api-modules.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index efe739a25..115ebbac2 100644
--- a/doc/ref/api-modules.texi
+++ b/doc/ref/api-modules.texi
@@ -212,10 +212,10 @@ and @var{seen} is the name in the using module. Note that @var{seen} is
also modified by @var{prefix} and @var{renamer}.
The @code{#:select}, @code{#:hide}, @code{#:prefix}, and
-@code{#:renamer} clauses are optional. If all are omitted, the returned
-interface has no bindings. If the @code{#:select} clause is omitted,
-@var{prefix} and @var{renamer} operate on the used module's public
-interface.
+@code{#:renamer} clauses are optional. If all are omitted, this form
+behaves identically to the previous one. If the @code{#:select} clause
+is omitted, @var{prefix} and @var{renamer} operate on the used module's
+public interface.
The @code{#:hide} operates on list of bindings in the module being
imported, before any renaming is performed. If both @code{#:select} and
--
2.45.1
next prev parent reply other threads:[~2024-06-27 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:17 bug#71800: [PATCH 0/2] Improve documentation about using modules Tomas Volf
2024-06-27 14:18 ` bug#71800: [PATCH 1/2] doc: Document #:hide Tomas Volf
2024-06-27 14:18 ` Tomas Volf [this message]
2024-07-02 3:31 ` bug#71800: [PATCH 0/2] Improve documentation about using modules Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20240627141852.30845-2-~@wolfsden.cz' \
--to=~@wolfsden.cz \
--cc=71800@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).