guile/guile-core/doc ChangeLog guile.texi indic...

[Martin Grabmueller]

CVSROOT:        /cvs
Module name:    guile
Changes by:     Martin Grabmueller <address@hidden>     01/05/23 10:24:50

Modified files:
        guile-core/doc : ChangeLog guile.texi indices.texi intro.texi 
                         scheme-data.texi scheme-evaluation.texi 
                         scheme-ideas.texi scheme-modules.texi 
                         scheme-procedures.texi srfi-modules.texi 

Log message:
        * guile.texi: Commented out menu entry and inclusion of Tcl/Tk
        stuff.
        
        * indices.texi: Users are advised to look under C and Scheme
        names, xref to transformation rules added.
        
        * intro.texi, scheme-modules.texi, scheme-ideas.texi,
        scheme-evaluation.texi, scheme-data.texi, scheme-procedures.texi:
        Fixed most REFFIXMEs.
        
        * srfi-modules.texi (About SRFI Usage): New node.
        (SRFI-0): Extended.
        Fixed all REFFIXMEs.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/ChangeLog.diff?cvsroot=OldCVS&tr1=1.92&tr2=1.93&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/guile.texi.diff?cvsroot=OldCVS&tr1=1.9&tr2=1.10&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/indices.texi.diff?cvsroot=OldCVS&tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/intro.texi.diff?cvsroot=OldCVS&tr1=1.9&tr2=1.10&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/scheme-data.texi.diff?cvsroot=OldCVS&tr1=1.18&tr2=1.19&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/scheme-evaluation.texi.diff?cvsroot=OldCVS&tr1=1.10&tr2=1.11&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/scheme-ideas.texi.diff?cvsroot=OldCVS&tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/scheme-modules.texi.diff?cvsroot=OldCVS&tr1=1.9&tr2=1.10&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/scheme-procedures.texi.diff?cvsroot=OldCVS&tr1=1.13&tr2=1.14&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/doc/srfi-modules.texi.diff?cvsroot=OldCVS&tr1=1.4&tr2=1.5&r1=text&r2=text

Patches:
Index: guile/guile-core/doc/ChangeLog
diff -u guile/guile-core/doc/ChangeLog:1.92 guile/guile-core/doc/ChangeLog:1.93
--- guile/guile-core/doc/ChangeLog:1.92 Tue May 22 16:26:36 2001
+++ guile/guile-core/doc/ChangeLog      Wed May 23 10:24:49 2001
@@ -1,3 +1,19 @@
+2001-05-23  Martin Grabmueller  <address@hidden>
+
+       * guile.texi: Commented out menu entry and inclusion of Tcl/Tk
+       stuff.
+
+       * indices.texi: Users are advised to look under C and Scheme
+       names, xref to transformation rules added.
+
+       * intro.texi, scheme-modules.texi, scheme-ideas.texi,
+       scheme-evaluation.texi, scheme-data.texi, scheme-procedures.texi:
+       Fixed most REFFIXMEs.
+
+       * srfi-modules.texi (About SRFI Usage): New node.
+       (SRFI-0): Extended.
+       Fixed all REFFIXMEs.
+
 2001-05-19  Neil Jerram  <address@hidden>
 
        * posix.texi (Networking): Split existing material into new nodes
Index: guile/guile-core/doc/guile.texi
diff -u guile/guile-core/doc/guile.texi:1.9 guile/guile-core/doc/guile.texi:1.10
--- guile/guile-core/doc/guile.texi:1.9 Mon May 14 14:37:51 2001
+++ guile/guile-core/doc/guile.texi     Wed May 23 10:24:49 2001
@@ -80,7 +80,7 @@
 @sp 10
 @comment The title is printed in a large font.
 @title Guile Reference Manual
address@hidden $Id: guile.texi,v 1.9 2001/05/14 21:37:51 mgrabmue Exp $
address@hidden $Id: guile.texi,v 1.10 2001/05/23 17:24:49 mgrabmue Exp $
 @subtitle For use with Guile @value{VERSION}
 @include AUTHORS
 
@@ -177,7 +177,7 @@
        add-on, so maybe it shouldn't be documented here
        (though it is nice to have a link from here to the
        Guile-scsh manual, if one exists).
-* Tcl/Tk Interface::
address@hidden * Tcl/Tk Interface::
 
 Part IV: Guile Scripting
 
@@ -255,7 +255,7 @@
 @include repl-modules.texi
 @include expect.texi
 @include scsh.texi
address@hidden tcltk.texi
address@hidden @include tcltk.texi
 
 @c Guile as an scripting language
 @iftex
Index: guile/guile-core/doc/indices.texi
diff -u guile/guile-core/doc/indices.texi:1.1 
guile/guile-core/doc/indices.texi:1.2
--- guile/guile-core/doc/indices.texi:1.1       Fri Mar  9 00:21:59 2001
+++ guile/guile-core/doc/indices.texi   Wed May 23 10:24:49 2001
@@ -1,22 +1,40 @@
 @node Concept Index
 @unnumbered Concept Index
+
+This index contains concepts, keywords and non-Schemey names for several
+features, to make it easier to locate the desired sections.
+
 @printindex cp
 
 
 @node Procedure Index
 @unnumbered Procedure Index
+
address@hidden FIXME::martin: Review me!
+
 This is an alphabetical list of all the procedures and macros in Guile.
-[[Remind people to look for functions under their Scheme names as well
-as their C names.]]
+
+When looking for a particular procedure, please look under its Scheme
+name as well as under its C name.  The C name can be constructed from
+the Scheme names by a simple transformation described in the section
address@hidden Scheme name to C name}.
+
 @printindex fn
 
 
 @node Variable Index
 @unnumbered Variable Index
+
address@hidden FIXME::martin: Review me!
+
 This is an alphabetical list of all the important variables and
 constants in Guile.
-[[Remind people to look for variables under their Scheme names as well
-as their C names.]]
+
+When looking for a particular variable or constant, please look under
+its Scheme name as well as under its C name.  The C name can be
+constructed from the Scheme names by a simple transformation described
+in the section @xref{Transforming Scheme name to C name}.
+
 @printindex vr
 
 
@@ -25,7 +43,9 @@
 @c spurious makeinfo errors.
 @node Type Index
 @unnumbered Type Index
+
 This is an alphabetical list of all the important data types defined in
 the Guile Programmers Manual.
+
 @printindex tp
 
Index: guile/guile-core/doc/intro.texi
diff -u guile/guile-core/doc/intro.texi:1.9 guile/guile-core/doc/intro.texi:1.10
--- guile/guile-core/doc/intro.texi:1.9 Wed May 16 11:08:12 2001
+++ guile/guile-core/doc/intro.texi     Wed May 23 10:24:49 2001
@@ -1,4 +1,4 @@
address@hidden $Id: intro.texi,v 1.9 2001/05/16 18:08:12 mgrabmue Exp $
address@hidden $Id: intro.texi,v 1.10 2001/05/23 17:24:49 mgrabmue Exp $
 
 @page
 @node What is Guile?
@@ -686,7 +686,7 @@
 directories listed in the @code{LTDL_LIBRRAY_PATH} environment variable.
 
 To see how these Guile extensions via shared libraries relate to the
-module system, see below REFFIXME.
+module system, see below @xref{Intro to Modules and Extensions}.
 
 @node Guile Modules
 @section Guile Modules
Index: guile/guile-core/doc/scheme-data.texi
diff -u guile/guile-core/doc/scheme-data.texi:1.18 
guile/guile-core/doc/scheme-data.texi:1.19
--- guile/guile-core/doc/scheme-data.texi:1.18  Wed May 16 11:08:12 2001
+++ guile/guile-core/doc/scheme-data.texi       Wed May 23 10:24:49 2001
@@ -1614,9 +1614,10 @@
 @subsection String Comparison
 
 The procedures in this section are similar to the character ordering
-predicates (REFFIXME), but are defined on character sequences.  They all
-return @code{#t} on success and @code{#f} on failure.  The predicates
-ending in @code{-ci} ignore the character case when comparing strings.
+predicates (@pxref{Characters}), but are defined on character sequences.
+They all return @code{#t} on success and @code{#f} on failure.  The
+predicates ending in @code{-ci} ignore the character case when comparing
+strings.
 
 
 @rnindex string=?
@@ -2536,7 +2537,7 @@
 @code{make-undefined-variable} or retrieved by @code{builtin-variable}.
 
 First-class variables are especially useful for interacting with the
-current module system (REFFIXME).
+current module system (@pxref{The Guile module system}).
 
 @deffn primitive builtin-variable name
 Return the built-in variable with the name @var{name}.
@@ -2967,7 +2968,7 @@
 
 This example also shows that lists have to be quoted (REFFIXME) when
 written, because they would otherwise be mistakingly taken as procedure
-applications (REFFIXME).
+applications (@pxref{Simple Invocation}).
 
 
 @node List Predicates
@@ -3028,7 +3029,7 @@
 of the old list.  On the other hand, applying procedures like
 @code{set-cdr!} or @code{delv!} to the new list will not alter the old
 list.  If you also need to copy the list elements (making a deep copy),
-use the procedure @code{copy-tree} (REFFIXME).
+use the procedure @code{copy-tree} (@pxref{Copying}).
 
 @node List Selection
 @subsection List Selection
@@ -4896,8 +4897,9 @@
 
 @subsection Vector Modification
 
-A vector created by any of the vector constructor procedures (REFFIXME)
-documented above can be modified using the following procedures.
+A vector created by any of the vector constructor procedures
+(@pxref{Vectors}) documented above can be modified using the
+following procedures.
 
 According to R5RS, using any of these procedures on literally entered
 vectors is an error, because these vectors are considered to be
Index: guile/guile-core/doc/scheme-evaluation.texi
diff -u guile/guile-core/doc/scheme-evaluation.texi:1.10 
guile/guile-core/doc/scheme-evaluation.texi:1.11
--- guile/guile-core/doc/scheme-evaluation.texi:1.10    Fri May  4 14:54:00 2001
+++ guile/guile-core/doc/scheme-evaluation.texi Wed May 23 10:24:49 2001
@@ -72,10 +72,10 @@
 comments}.  This type of comment begins with the character sequence
 @code{#!} and ends with the characters @code{!#}, which must appear on a
 line of their own.  These comments are compatible with the block
-comments in the Scheme Shell @file{scsh} (REFFIXME).  The characters
address@hidden were chosen because they are the magic characters used in
-shell scripts for indicating that the name of the program for executing
-the script follows on the same line.
+comments in the Scheme Shell @file{scsh} (@pxref{The Scheme shell
+(scsh)}).  The characters @code{#!} were chosen because they are the
+magic characters used in shell scripts for indicating that the name of
+the program for executing the script follows on the same line.
 
 Thus a Guile script often starts like this.
 
@@ -85,7 +85,7 @@
 @end lisp
 
 More details on Guile scripting can be found in the scripting section
-(REFFIXME).
+(@pxref{Guile Scripting}).
 
 
 @node Case Sensitivity
@@ -105,7 +105,7 @@
 
 It is possible to turn off case sensitivity in Guile by setting the
 reader option @code{case-insensitive}.  More on reader options can be
-found at (REFFIXME).
+found at (@pxref{Reader options}).
 
 @lisp
 (read-enable 'case-insensitive)
Index: guile/guile-core/doc/scheme-ideas.texi
diff -u guile/guile-core/doc/scheme-ideas.texi:1.1 
guile/guile-core/doc/scheme-ideas.texi:1.2
--- guile/guile-core/doc/scheme-ideas.texi:1.1  Fri Mar  9 00:22:00 2001
+++ guile/guile-core/doc/scheme-ideas.texi      Wed May 23 10:24:49 2001
@@ -178,10 +178,10 @@
 
 @itemize @bullet
 @item
-REFFIXME, to read about using @code{define} other than at top level in a
-Scheme program, including a discussion of when it works to use
address@hidden rather than @code{set!} to change the value of an existing
-variable.
address@hidden Definitions}, to read about using @code{define} other
+than at top level in a Scheme program, including a discussion of when it
+works to use @code{define} rather than @code{set!} to change the value
+of an existing variable.
 
 @item
 @ref{Lambda Alternatives}, to read about an alternative form of the
@@ -815,39 +815,39 @@
 when you see it.  For a full description of each of these syntaxes,
 follow the appropriate reference.
 
address@hidden (REFFIXME) and @code{cond} (REFFIXME) provide conditional
address@hidden and @code{cond} (@pxref{if cond case}) provide conditional
 evaluation of argument expressions depending on whether one or more
 conditions evaluate to ``true'' or ``false''.
 
address@hidden (REFFIXME) provides conditional evaluation of argument
-expressions depending on whether a variable has one of a specified group
-of values.
address@hidden (@pxref{if cond case}) provides conditional evaluation of
+argument expressions depending on whether a variable has one of a
+specified group of values.
 
 @code{define} (REFFIXME) is used to create a new variable and set its
 initial value.
 
 @code{set!} (REFFIXME) is used to modify an existing variable's value.
 
address@hidden (REFFIXME) is used to construct procedure objects.
address@hidden (@pxref{Lambda}) is used to construct procedure objects.
 
address@hidden (REFFIXME), @code{let*} (REFFIXME) and @code{letrec}
-(REFFIXME) create an inner lexical environment for the evaluation of a
-sequence of expressions, in which a specified set of local variables is
-bound to the values of a corresponding set of expressions.  For an
-introduction to environments, see @xref{About Closure}.
address@hidden, @code{let*} and @code{letrec} (@pxref{Local Bindings})
+create an inner lexical environment for the evaluation of a sequence of
+expressions, in which a specified set of local variables is bound to the
+values of a corresponding set of expressions.  For an introduction to
+environments, see @xref{About Closure}.
 
address@hidden (REFFIXME) executes a sequence of expressions in order and
-returns the value of the last expression.  Note that this is not the
address@hidden (@pxref{begin}) executes a sequence of expressions in order
+and returns the value of the last expression.  Note that this is not the
 same as a procedure which returns its last argument, because the
 evaluation of a procedure invocation expression does not guarantee to
 evaluate the arguments in order.
 
address@hidden (REFFIXME) executes a sequence of expressions in order until
-either there are no expressions left, or one of them evaluates to
address@hidden (@pxref{and or}) executes a sequence of expressions in order
+until either there are no expressions left, or one of them evaluates to
 ``false''.
 
address@hidden (REFFIXME) executes a sequence of expressions in order until
-either there are no expressions left, or one of them evaluates to
address@hidden (@pxref{and or}) executes a sequence of expressions in order
+until either there are no expressions left, or one of them evaluates to
 ``true''.
 
 
@@ -938,9 +938,9 @@
 that are more limited in their scope, typically as part of a procedure
 body.  In Scheme, this is done using the @code{let} syntax, or one of
 its modified forms @code{let*} and @code{letrec}.  These syntaxes are
-described in full later in the manual (REFFIXME).  Here our purpose is
-to illustrate their use just enough that we can see how local variables
-work.
+described in full later in the manual (@pxref{Local Bindings}).  Here
+our purpose is to illustrate their use just enough that we can see how
+local variables work.
 
 For example, the following code uses a local variable @code{s} to
 simplify the computation of the area of a triangle given the lengths of
Index: guile/guile-core/doc/scheme-modules.texi
diff -u guile/guile-core/doc/scheme-modules.texi:1.9 
guile/guile-core/doc/scheme-modules.texi:1.10
--- guile/guile-core/doc/scheme-modules.texi:1.9        Sun May 13 12:14:41 2001
+++ guile/guile-core/doc/scheme-modules.texi    Wed May 23 10:24:50 2001
@@ -394,38 +394,38 @@
 Guile's support for multi threaded execution (@pxref{Scheduling}).
 
 @item (ice-9 rdelim)
-Line- and character-delimited input (REFFIXME).
+Line- and character-delimited input (@pxref{Line/Delimited}).
 
 @item (ice-9 documentation)
 Online documentation (REFFIXME).
 
 @item (srfi srfi-2)
-Support for @code{and-let*} (REFFIXME).
+Support for @code{and-let*} (@pxref{SRFI-2}).
 
 @item (srfi srfi-6)
-Support for some additional string port procedures (REFFIXME).
+Support for some additional string port procedures (@pxref{SRFI-6}).
 
 @item (srfi srfi-8)
-Multiple-value handling with @code{receive} (REFFIXME).
+Multiple-value handling with @code{receive} (@pxref{SRFI-8}).
 
 @item (srfi srfi-9)
-Record definition with @code{define-record-type} (REFFIXME).
+Record definition with @code{define-record-type} (@pxref{SRFI-9}).
 
 @item (srfi srfi-10)
-Read hash extension @code{#,()} (REFFIXME).
+Read hash extension @code{#,()} (@pxref{SRFI-10}).
 
 @item (srfi srfi-11)
 Multiple-value handling with @code{let-values} and @code{let-values*}
-(REFFIXME).
+(@pxref{SRFI-11}).
 
 @item (srfi srfi-13)
-String library (REFFIXME).
+String library (@pxref{SRFI-13}).
 
 @item (srfi srfi-14)
-Character-set library (REFFIXME).
+Character-set library (@pxref{SRFI-14}).
 
 @item (srfi srfi-17)
-Getter-with-setter support (REFFIXME).
+Getter-with-setter support (@pxref{SRFI-17}).
 
 @item (ice-9 slib)
 This module contains hooks for using Aubrey Jaffer's portable Scheme
Index: guile/guile-core/doc/scheme-procedures.texi
diff -u guile/guile-core/doc/scheme-procedures.texi:1.13 
guile/guile-core/doc/scheme-procedures.texi:1.14
--- guile/guile-core/doc/scheme-procedures.texi:1.13    Wed May 16 12:30:57 2001
+++ guile/guile-core/doc/scheme-procedures.texi Wed May 23 10:24:50 2001
@@ -124,7 +124,7 @@
 destructuring rest argument lists and giving names to the various list
 elements.  @code{let-optional} binds all variables simultaneously, while
 @code{let-optional*} binds them sequentially, consistent with @code{let}
-and @code{let*} (REFFIXME).
+and @code{let*} (@pxref{Local Bindings}).
 
 @deffn {libary syntax} let-optional rest-arg (binding @dots{}) expr @dots{}
 @deffnx {library syntax} let-optional* rest-arg (binding @dots{}) expr @dots{}
@@ -155,7 +155,7 @@
 
 @code{let-keywords} binds all variables simultaneously, while
 @code{let-keywords*} binds them sequentially, consistent with @code{let}
-and @code{let*} (REFFIXME).
+and @code{let*} (@pxref{Local Bindings}).
 
 @deffn {library syntax} let-keywords rest-arg allow-other-keys? (binding 
@dots{})  expr @dots{}
 @deffnx {library syntax} let-keywords rest-arg allow-other-keys? (binding 
@dots{})  expr @dots{}
@@ -345,7 +345,6 @@
 for any kind of procedure.  @code{closure?} does not return @code{#t}
 for primitive procedures, and @code{thunk?} only returns @code{#t} for
 procedures which do not accept any arguments.
address@hidden FIXME::martin: thunk? returns true for `id'.  What's wrong here?
 
 @rnindex procedure?
 @deffn primitive procedure? obj
Index: guile/guile-core/doc/srfi-modules.texi
diff -u guile/guile-core/doc/srfi-modules.texi:1.4 
guile/guile-core/doc/srfi-modules.texi:1.5
--- guile/guile-core/doc/srfi-modules.texi:1.4  Wed May 16 12:30:57 2001
+++ guile/guile-core/doc/srfi-modules.texi      Wed May 23 10:24:50 2001
@@ -1,6 +1,6 @@
 @page
 @node SRFI Support
address@hidden Various SRFI Support Modules
address@hidden SRFI Support Modules
 
 SRFI is an acronym for Scheme Request For Implementation.  The SRFI
 documents define a lot of syntactic and procedure extensions to standard
@@ -13,6 +13,7 @@
 @url{http://srfi.schemers.org}.
 
 @menu
+* About SRFI Usage::            What to know about Guile's SRFI support.
 * SRFI-0::                      cond-expand
 * SRFI-2::                      and-let*.
 * SRFI-6::                      Basic String Ports.
@@ -27,6 +28,40 @@
 @end menu
 
 
address@hidden About SRFI Usage
address@hidden About SRFI Usage
+
address@hidden FIXME::martin: Review me!
+
+SRFI support in Guile is currently implemented partly in the core
+library, and partly as add-on modules.  That means that some SRFIs are
+automatically available when the interpreter is started, whereas the
+other SRFIs require you to use the appropriate support module
+explicitly.  
+
+There are several reasons for this inconsistency.  First, the feature
+checking syntactic form @code{cond-expand} (@pxref{SRFI-0}) must be
+available immediately, because it must be there when the user wants to
+check for the Scheme implementation, that is, before she can know that
+it is safe to use @code{use-modules} to load SRFI support modules.  The
+second reason is that some features defined in SRFIs had been
+implemented in Guile before the developers started to add SRFI
+implementations as modules (for example SRFI-6 (@pxref{SRFI-6})).  In
+the future, it is possible that SRFIs in the core library might be
+factored out into separate modules, requiring explicit module loading
+when they are needed.  So you should be prepared to have to use
address@hidden someday in the future to access SRFI-6 bindings.  If
+you want, you can do that already.  We have included the module
address@hidden(srfi srfi-6)} in the distribution, which currently does nothing,
+but ensures that you can write future-safe code.
+
+Generally, support for a specific SRFI is made available by using
+modules named @code{(srfi address@hidden)}, where @var{number} is the
+number of the SRFI needed.  Another possibility is to use the command
+line option @code{--use-srfi}, which will load the necessary modules
+automatically (@pxref{Invoking Guile}).
+
+
 @node SRFI-0
 @section SRFI-0 - cond-expand
 
@@ -78,6 +113,8 @@
 clause, it is satisfied if no prior clause matched.
 @end itemize
 
+If no clause is satisfied, an error is signalled.
+
 Since @code{cond-expand} is needed to tell what a Scheme implementation
 provides, it must be accessible without using any
 implementation-dependant operations, such as @code{use-modules} in
@@ -85,11 +122,13 @@
 this form.
 
 Currently, the feature identifiers @code{guile}, @code{r5rs} and
address@hidden are supported.  The other SRFIs are not in that list,
-because the SRFI modules must be explicitly used before their exported
-bindings can be used.  So if a Scheme program wishes to detect whether
-SRFI-8 is supported in the running implementation, code similar to this
-may be needed:
address@hidden are supported.  The other SRFIs are not in that list by
+default, because the SRFI modules must be explicitly used before their
+exported bindings can be used.  
+
+So if a Scheme program wishes to use SRFI-8, it has two possibilities:
+First, it can check whether the running Scheme implementation is Guile,
+and if it is, it can use the appropriate module:
 
 @lisp
 (cond-expand
@@ -100,6 +139,23 @@
   ;; otherwise fail.
 @end lisp
 
+The other possibility is to use the @code{--use-srfi} command line
+option when invoking Guile (@pxref{Invoking Guile}).  When you do that,
+the specified SRFI support modules will be loaded and add their feature
+identifier to the list of symbols checked by @code{cond-expand}.
+
+So, if you invoke Guile like this:
+
address@hidden
+$ guile --use-srfi=8
address@hidden example
+
+the following snippet will expand to @code{'hooray}.
+
address@hidden
+(cond-expand (srfi-8 'hooray))
address@hidden lisp
+
 
 @node SRFI-2
 @section SRFI-2 - and-let*
@@ -154,7 +210,7 @@
 
 This is the SRFI way for defining record types.  The Guile
 implementation is a layer above Guile's normal record construction
-procedures (REFFIXME).  The nice thing about this kind of record
+procedures (@pxref{Records}).  The nice thing about this kind of record
 definition method is that no new names are implicitly created, all
 constructor, accessor and predicates are explicitly given.  This reduces
 the risk of variable capture.
@@ -242,8 +298,8 @@
 
 This module implements the binding forms for multiple values
 @code{let-values} and @code{let-values*}.  These forms are similar to
address@hidden and @code{let*} (REFFIXME), but they support binding of the
-values returned by multiple-valued expressions.
address@hidden and @code{let*} (@pxref{Local Bindings}), but they support
+binding of the values returned by multiple-valued expressions.
 
 Write @code{(use-modules (srfi srfi-11))} to make the bindings
 available.
@@ -272,7 +328,8 @@
 Note that only the procedures from SRFI-13 are documented here which are
 not already contained in Guile.  For procedures not documented here
 please refer to the relevant chapters in the Guile Reference Manual, for
-example the documentation of strings and string procedures (REFFIXME).
+example the documentation of strings and string procedures
+(@pxref{Strings}).
 
 All of the procedures defined in SRFI-13, which are not already included
 in the Guile core library, are implemented in the module @code{(srfi
@@ -387,7 +444,8 @@
 The procedure @code{string->list} is extended by SRFI-13, that is why it
 is included in @code{(srfi srfi-13)}.  The other procedures are new.
 The Guile core already contains the procedure @code{list->string} for
-converting a list of characters into a string (REFFIXME).
+converting a list of characters into a string (@pxref{List/String
+Conversion}).
 
 @deffn primitive string->list str [start end]
 Convert the string @var{str} into a list of characters.
@@ -436,7 +494,8 @@
 information about the string or select pieces of a given string.
 
 Additional selector procedures are documented in the Strings section
-(REFFIXME), like @code{string-length} or @code{string-ref}.
+(@pxref{String Selection}), like @code{string-length} or
address@hidden
 
 @code{string-copy} is also available in core Guile, but this version
 accepts additional start/end indices.
@@ -512,7 +571,8 @@
 The procedure @code{string-fill!} is extended from R5RS because it
 accepts optional start/end indices.  This bindings shadows the procedure
 of the same name in the Guile core.  The second modification procedure
address@hidden is documented in the Strings section (REFFIXME).
address@hidden is documented in the Strings section (@pxref{String
+Modification}).
 
 @deffn primitive string-fill! str chr [start end]
 Stores @var{chr} in every element of the given @var{str} and
@@ -943,9 +1003,10 @@
 @node SRFI-14 Character Set Data Type
 @subsection Character Set Data Type
 
-The data type @dfn{charset} implements sets of characters (REFFIXME).
-Because the internal representation of character sets is not visible to
-the user, a lot of procedures for handling them are provided.
+The data type @dfn{charset} implements sets of characters
+(@pxref{Characters}).  Because the internal representation of character
+sets is not visible to the user, a lot of procedures for handling them
+are provided.
 
 Character sets can be created, extended, tested for the membership of a
 characters and be compared to other character sets.
@@ -1327,8 +1388,8 @@
 The value returned by a @code{case-lambda} form is a procedure which
 matches the number of actual arguments against the formals in the
 various clauses, in order.  @dfn{Formals} means a formal argument list
-just like with @code{lambda} (REFFIXME). The first matching clause is
-selected, the corresponding values from the actual parameter list are
+just like with @code{lambda} (@pxref{Lambda}). The first matching clause
+is selected, the corresponding values from the actual parameter list are
 bound to the variable names in the clauses and the body of the clause is
 evaluated.  If no clause matches, an error is signalled.
 
@@ -1382,3 +1443,4 @@
 procedure is to create a new object (a @dfn{procedure with setter}) via
 the @code{getter-with-setter} procedure. This procedure is also
 specified in the SRFI.  Using it avoids the described problems.
+