1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-05-28 16:00:22 +02:00

Cross reference 'SRFI-9 Records' directly instead of 'SRFI-9'.

* doc/ref/api-compound.texi (Record Overview, Records):
  doc/ref/api-modules.texi (Included Guile Modules):
  doc/ref/r6rs.texi (R6RS Records): Cross reference 'SRFI-9 Records'
  directly instead of 'SRFI-9'.
This commit is contained in:
Mark H Weaver 2013-04-04 03:16:42 -04:00
parent 4120539225
commit 71539c1cd3
3 changed files with 8 additions and 7 deletions

View file

@ -2211,9 +2211,9 @@ different trade-offs. Over the years, each ``standard'' has also come
with its own new record interface, leading to a maze of record APIs. with its own new record interface, leading to a maze of record APIs.
At the highest level is SRFI-9, a high-level record interface At the highest level is SRFI-9, a high-level record interface
implemented by most Scheme implementations (@pxref{SRFI-9}). It defines implemented by most Scheme implementations (@pxref{SRFI-9 Records}). It
a simple and efficient syntactic abstraction of record types and their defines a simple and efficient syntactic abstraction of record types and
associated type predicate, fields, and field accessors. SRFI-9 is their associated type predicate, fields, and field accessors. SRFI-9 is
suitable for most uses, and this is the recommended way to create record suitable for most uses, and this is the recommended way to create record
types in Guile. Similar high-level record APIs include SRFI-35 types in Guile. Similar high-level record APIs include SRFI-35
(@pxref{SRFI-35}) and R6RS records (@pxref{rnrs records syntactic}). (@pxref{SRFI-35}) and R6RS records (@pxref{rnrs records syntactic}).
@ -2451,7 +2451,7 @@ data type. A @dfn{record} is an instance of a record type.
Note that in many ways, this interface is too low-level for every-day Note that in many ways, this interface is too low-level for every-day
use. Most uses of records are better served by SRFI-9 records. use. Most uses of records are better served by SRFI-9 records.
@xref{SRFI-9}. @xref{SRFI-9 Records}.
@deffn {Scheme Procedure} record? obj @deffn {Scheme Procedure} record? obj
Return @code{#t} if @var{obj} is a record of any type and @code{#f} Return @code{#t} if @var{obj} is a record of any type and @code{#f}

View file

@ -1144,7 +1144,8 @@ Support for some additional string port procedures (@pxref{SRFI-6}).
Multiple-value handling with @code{receive} (@pxref{SRFI-8}). Multiple-value handling with @code{receive} (@pxref{SRFI-8}).
@item (srfi srfi-9) @item (srfi srfi-9)
Record definition with @code{define-record-type} (@pxref{SRFI-9}). Record definition with @code{define-record-type} (@pxref{SRFI-9
Records}).
@item (srfi srfi-10) @item (srfi srfi-10)
Read hash extension @code{#,()} (@pxref{SRFI-10}). Read hash extension @code{#,()} (@pxref{SRFI-10}).

View file

@ -826,11 +826,11 @@ This form is identical to the one provided by Guile's core library.
@node R6RS Records @node R6RS Records
@subsubsection R6RS Records @subsubsection R6RS Records
The manual sections below describe Guile's implementation of R6RS The manual sections below describe Guile's implementation of R6RS
records, which provide support for user-defined data types. The R6RS records, which provide support for user-defined data types. The R6RS
records API provides a superset of the features provided by Guile's records API provides a superset of the features provided by Guile's
``native'' records, as well as those of the SRFI-9 records API; ``native'' records, as well as those of the SRFI-9 records API;
@xref{Records}, and @ref{SRFI-9}, for a description of those @xref{Records}, and @ref{SRFI-9 Records}, for a description of those
interfaces. interfaces.
As with SRFI-9 and Guile's native records, R6RS records are constructed As with SRFI-9 and Guile's native records, R6RS records are constructed