From: "Dr. Arne Babenhauserheide" via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 72208@debbugs.gnu.org
Cc: guile-devel@gnu.org
Subject: bug#72208: [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi
Date: Sat, 20 Jul 2024 17:03:01 +0200 [thread overview]
Message-ID: <87y15wjeca.fsf__44074.4546403707$1721487865$gmane$org@web.de> (raw)
In-Reply-To: <handler.72208.B.17214811119924.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Sat, 20 Jul 2024 13:12:02 +0000")
[-- Attachment #1.1: Type: text/plain, Size: 152 bytes --]
Hi,
Following my answer in the discussion (after checking the non-ice-9
prefixes), this may be a better representation of the modules Guile
provides:
[-- Attachment #1.2: 0001-doc-reference-ice-9-scheme-and-srfi.patch --]
[-- Type: text/x-patch, Size: 1629 bytes --]
From 6838e4da9712425e7e45805a73731bb399d90a86 Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide <arne_bab@web.de>
Date: Sat, 20 Jul 2024 15:03:15 +0200
Subject: [PATCH] doc: reference ice-9, scheme, and srfi
* doc/ref/tour.texi (Using Modules): reference ice-9, scheme, and srfi.
---
doc/ref/tour.texi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/ref/tour.texi b/doc/ref/tour.texi
index c0ecb1699..91eb10bb9 100644
--- a/doc/ref/tour.texi
+++ b/doc/ref/tour.texi
@@ -210,6 +210,16 @@ processing or command line parsing. Additionally, there exist many
Guile modules written by other Guile hackers, but which have to be
installed manually.
+Most provided modules use prefixes based on their origin:
+
+@itemize @bullet
+@item @code{ice-9} includes guile-specific modules: the standard library of Guile. @xref{Status, History of ice-9, History of ice-9}
+@item @code{rnrs} and @code{scheme} include modules from the RnRS standard (@url{https://standards.scheme.org/}). @xref{R7RS Support} and @xref{R6RS Support}
+@item @code{srfi} includes Scheme Requests For Implementation; SRFI’s (@url{https://srfi.schemers.org/}). @xref{SRFI Support}
+@item Some larger features have their own prefix. These include @code{web} (@pxref{Web}), @code{oop} (@xref{GOOPS}), @code{sxml} (@pxref{SXML}), and @code{language} (@pxref{Other Languages}).
+@end itemize
+
+
Here is a sample interactive session that shows how to use the
@code{(ice-9 popen)} module which provides the means for communicating
with other processes over pipes together with the @code{(ice-9
--
2.45.1
[-- Attachment #1.3: Type: text/plain, Size: 101 bytes --]
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
prev parent reply other threads:[~2024-07-20 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 13:11 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi Dr. Arne Babenhauserheide
[not found] ` <handler.72208.B.17214811119924.ack@debbugs.gnu.org>
2024-07-20 15:03 ` Dr. Arne Babenhauserheide via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
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='87y15wjeca.fsf__44074.4546403707$1721487865$gmane$org@web.de' \
--to=bug-guile@gnu.org \
--cc=72208@debbugs.gnu.org \
--cc=arne_bab@web.de \
--cc=guile-devel@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).