From: Kevin Ryde <user42@zip.com.au>
Subject: doco srfi indexing
Date: Tue, 13 May 2003 09:31:21 +1000 [thread overview]
Message-ID: <87k7cv214m.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 146 bytes --]
FYI, I added more indexing to the srfis,
* srfi-modules.texi: Add indexing of srfi numbers, and a couple of
procedures not otherwise indexed.
[-- Attachment #2: srfi-modules.texi.indexing.diff --]
[-- Type: text/plain, Size: 3520 bytes --]
--- srfi-modules.texi.~1.11.~ 2003-05-04 08:38:05.000000000 +1000
+++ srfi-modules.texi 2003-05-13 09:28:29.000000000 +1000
@@ -1,6 +1,7 @@
@page
@node SRFI Support
@chapter SRFI Support Modules
+@cindex SRFI
SRFI is an acronym for Scheme Request For Implementation. The SRFI
documents define a lot of syntactic and procedure extensions to standard
@@ -67,6 +68,7 @@
@node SRFI-0
@section SRFI-0 - cond-expand
+@cindex SRFI-0
@c FIXME::martin: Review me!
@@ -164,6 +166,7 @@
@node SRFI-1
@section SRFI-1 - List library
+@cindex SRFI-1
@c FIXME::martin: Review me!
@@ -840,9 +843,11 @@
@node SRFI-2
@section SRFI-2 - and-let*
+@cindex SRFI-2
@c FIXME::martin: Review me!
+@findex and-let*
The syntactic form @code{and-let*} combines the conditional evaluation
form @code{and} with the binding form @var{let*}. Each argument
expression will be evaluated sequentially, bound to a variable (if a
@@ -871,6 +876,7 @@
@node SRFI-4
@section SRFI-4 - Homogeneous numeric vector datatypes.
+@cindex SRFI-4
@c FIXME::martin: Review me!
@@ -996,6 +1002,7 @@
@node SRFI-6
@section SRFI-6 - Basic String Ports
+@cindex SRFI-6
SRFI-6 defines the procedures @code{open-input-string},
@code{open-output-string} and @code{get-output-string}. These
@@ -1006,6 +1013,7 @@
@node SRFI-8
@section SRFI-8 - receive
+@cindex SRFI-8
@code{receive} is a syntax for making the handling of multiple-value
procedures easier. It is documented in @xref{Multiple Values}.
@@ -1013,6 +1021,7 @@
@node SRFI-9
@section SRFI-9 - define-record-type
+@cindex SRFI-9
This is the SRFI way for defining record types. The Guile
implementation is a layer above Guile's normal record construction
@@ -1063,6 +1072,7 @@
@node SRFI-10
@section SRFI-10 - Hash-Comma Reader Extension
+@cindex SRFI-10
@cindex hash-comma
@cindex #,()
@@ -1104,7 +1114,10 @@
@node SRFI-11
@section SRFI-11 - let-values
+@cindex SRFI-11
+@findex let-values
+@findex let-values*
This module implements the binding forms for multiple values
@code{let-values} and @code{let-values*}. These forms are similar to
@code{let} and @code{let*} (@pxref{Local Bindings}), but they support
@@ -1130,6 +1143,7 @@
@node SRFI-13
@section SRFI-13 - String Library
+@cindex SRFI-13
In this section, we will describe all procedures defined in SRFI-13
(string library) and implemented by the module @code{(srfi srfi-13)}.
@@ -1773,6 +1787,7 @@
@node SRFI-14
@section SRFI-14 - Character-set Library
+@cindex SRFI-14
SRFI-14 defines the data type @dfn{character set}, and also defines a
lot of procedures for handling this character type, and a few standard
@@ -2173,9 +2188,11 @@
@node SRFI-16
@section SRFI-16 - case-lambda
+@cindex SRFI-16
@c FIXME::martin: Review me!
+@findex case-lambda
The syntactic form @code{case-lambda} creates procedures, just like
@code{lambda}, but has syntactic extensions for writing procedures of
varying arity easier.
@@ -2236,9 +2253,11 @@
@node SRFI-17
@section SRFI-17 - Generalized set!
+@cindex SRFI-17
This is an implementation of SRFI-17: Generalized set!
+@findex getter-with-setter
It exports the Guile procedure @code{make-procedure-with-setter} under
the SRFI name @code{getter-with-setter} and exports the standard
procedures @code{car}, @code{cdr}, @dots{}, @code{cdddr},
@@ -2258,6 +2277,7 @@
@node SRFI-19
@section SRFI-19 - Time/Date Library
+@cindex SRFI-19
This is an implementation of SRFI-19: Time/Date Library
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-05-12 23:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87k7cv214m.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).