commit 88e6dcaae04b72fd2bbe0537a7d25a6c4fbd4522
parent c6fd58dd0131f8a2835093c36b682e3f0fc7b1e2
Author: Wolfgang Corcoran-Mathe <wcm@sigwinch.xyz>
Date: Mon, 5 Feb 2024 14:11:38 -0500
Fix typos.
Diffstat:
2 files changed, 12 insertions(+), 80 deletions(-)
diff --git a/doc/r7rs-small/lexical-conventions.texinfo b/doc/r7rs-small/lexical-conventions.texinfo
@@ -102,8 +102,10 @@ The lexical syntax includes several comment forms. Comments are treated exactly
whitespace.
A semicolon (@samp{;}) indicates the start of a line comment. The comment continues to the end
-of the line on which the semicolon appears. Another way to indicate a comment is to
-prefix a @svar{datum} (cf. @ref{External representations}) with @code{#;} and optional @svar{whitespace}. The comment
+of the line on which the semicolon appears.
+
+Another way to indicate a comment is to
+prefix a @svar{datum} (cf. @ref{External representations formal}) with @code{#;} and optional @svar{whitespace}. The comment
consists of the comment prefix @code{#;}, the space, and the @svar{datum} together. This notation is
useful for ``commenting out'' sections of code.
diff --git a/doc/r7rs-small/overview.texinfo b/doc/r7rs-small/overview.texinfo
@@ -116,7 +116,7 @@ Must support portable code by providing a mode of operation in which the lexical
When speaking of an error situation, this report uses the phrase ``an error is signaled'' to
indicate that implementations must detect and report the error. An error is signaled by
raising a non-continuable exception, as if by the procedure @code{raise} as described in
-@{Exceptions}. The object raised is implementation-dependent and need not be distinct from
+@ref{Exceptions}. The object raised is implementation-dependent and need not be distinct from
objects previously used for the same purpose. In addition to errors signaled in situations
described in this report, programmers can signal their own errors and handle signaled
errors.
@@ -160,85 +160,15 @@ programmer or program behavior.
@node Entry format
@subsection Entry format
-@c To what extent should the Texinfo version follow the PDF's
-@c formatting?
+@strong{This section is incomplete. The Texinfo entry format differs
+from that of the @rsevenrs{} PDF, and may be described here when the
+format is stable.}
-Chapters @ref{Expressions} and @{Standard procedures} are organized into entries. Each entry describes one language feature
+Chapters @ref{Expressions} and @ref{Standard procedures} are organized into entries. Each entry describes one language feature
or a group of related features, where a feature is either a syntactic construct or a
-procedure. An entry begins with one or more header lines of the form
+procedure.
-category:
-
-template
-
-
-for identifiers in the base library, or
-
-name library
-
-category:
-
-template
-
-
-where
-
-name is the short name of a library as defined in @ref{Appendix A}.
-
-If
-
-category is ``syntax,'' the entry describes an expression type, and the template gives the
-syntax of the expression type. Components of expressions are designated by syntactic
-variables, which are written using angle brackets, for example @svar{expression} and
-@svar{variable}. Syntactic variables are intended to denote segments of program text; for
-example, @svar{expression} stands for any string of characters which is a syntactically valid
-expression. The notation
-
-@display
-@svar{thing@sub{1}} @dots{}
-@end display
-
-indicates zero or more occurrences of a @svar{thing}, and
-
-@display
-@svar{thing@sub{1}} @svar{thing@sub{2}} @dots{}
-@end display
-
-indicates one or more occurrences of a @svar{thing}.
-
-If
-
-category is ``auxiliary syntax,'' then the entry describes a syntax binding that occurs only as
-part of specific surrounding expressions. Any use as an independent syntactic construct
-or variable is an error.
-
-If
-
-category is ``procedure,'' then the entry describes a procedure, and the header line gives a
-template for a call to the procedure. Argument names in the template are
-
-italicized. Thus the header line
-
-@deffn procedure vector-ref vector k
-
-indicates that the procedure bound to the @code{vector-ref} variable takes two arguments, a
-vector
-
-@var{vector} and an exact non-negative integer
-
-@var{k} (see below).
-
-@end deffn
-
-The header lines
-
-@deffn procedure make-vector k
-@deffnx procedure make-vector k fill
-
-indicate that the @code{make-vector} procedure must be defined to take either one or two
-arguments.
-
-@end deffn
+[@dots{}]
It is an error for a procedure to be presented with an argument that it is not specified to
handle. For succinctness, we follow the convention that if an argument name is also the
@@ -273,7 +203,7 @@ exact non-negative integer
alphabetic character
@item @var{list}, @var{list}@sub{1}, @dots{} @var{list}@sub{@var{j}}, @dots{}
-list (see @{Pairs and lists})
+list (see @ref{Pairs and lists})
@item @var{n}, @var{n}@sub{1}, @dots{} @var{n}@sub{@var{j}}, @dots{}
integer
