From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: guile-devel@gnu.org, bug-guile@gnu.org
Subject: [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi
Date: Sat, 20 Jul 2024 15:11:41 +0200 [thread overview]
Message-ID: <87plr8ky2a.fsf@web.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 250 bytes --]
Hi,
the attached patch is a companion to the thread "The Guile junk drawer
and a C plea" in guile-devel.
Its goal is to ensure that newcomers learn early about the main module
prefixes provided by Guile: (scheme ...), (srfi ...), and (ice-9 ...).
[-- Attachment #1.2: 0001-doc-reference-ice-9-scheme-and-srfi.patch --]
[-- Type: text/x-patch, Size: 1352 bytes --]
From 929f5075be5d21c552e91931aca4a68fde348e21 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 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/ref/tour.texi b/doc/ref/tour.texi
index c0ecb1699..7142394a5 100644
--- a/doc/ref/tour.texi
+++ b/doc/ref/tour.texi
@@ -210,6 +210,15 @@ 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 one of three different prefixes:
+
+@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{scheme} includes modules from the RnRS standard: @url{https://standards.scheme.org/}.
+@item @code{srfi} includes Scheme Requests For Implementation; SRFI’s: @url{https://srfi.schemers.org/}.
+@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: 312 bytes --]
There may be more places where it could be useful to add references, so
newcomers are guided to easily know their way around what Guile
provides. This is the most obvious place I found, so I started there.
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 --]
next reply other threads:[~2024-07-20 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 13:11 Dr. Arne Babenhauserheide [this message]
[not found] ` <handler.72208.B.17214811119924.ack@debbugs.gnu.org>
2024-07-20 15:03 ` bug#72208 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi Dr. Arne Babenhauserheide
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=87plr8ky2a.fsf@web.de \
--to=arne_bab@web.de \
--cc=bug-guile@gnu.org \
--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).