Fixes typos pointed out in #353
original commit: ebee5db8fac9639bd88f313ef0c4a0641dba8317
This commit is contained in:
parent
75a70547f8
commit
03ae461f54
|
@ -49,7 +49,7 @@ albeit scoped where the bindings of the \scheme{let-syntax} or
|
||||||
in a library or RNRS top-level program unless the
|
in a library or RNRS top-level program unless the
|
||||||
\scheme{scheme} library is included in the library or
|
\scheme{scheme} library is included in the library or
|
||||||
top-level programs imports.
|
top-level programs imports.
|
||||||
These forms are described in Chatper~\ref{CHPTSYNTAX}.
|
These forms are described in Chapter~\ref{CHPTSYNTAX}.
|
||||||
|
|
||||||
In Revised$^6$ Report Scheme, definitions can appear at the front of
|
In Revised$^6$ Report Scheme, definitions can appear at the front of
|
||||||
a \scheme{lambda} or similar body (e.g., a \scheme{let} or \scheme{letrec}
|
a \scheme{lambda} or similar body (e.g., a \scheme{let} or \scheme{letrec}
|
||||||
|
@ -66,8 +66,8 @@ procedure.
|
||||||
The macro expander uses the same two-pass algorithm for expanding
|
The macro expander uses the same two-pass algorithm for expanding
|
||||||
top-level \scheme{begin} expressions as it uses for a \scheme{lambda},
|
top-level \scheme{begin} expressions as it uses for a \scheme{lambda},
|
||||||
\scheme{library}, or top-level program body.
|
\scheme{library}, or top-level program body.
|
||||||
(This algorithm is described in Section~\ref{SECTSYNTAXDEFINITIONS} of {\TSPLFOUR}.)
|
(This algorithm is described in Section~\ref{TSPL:SECTSYNTAXDEFINITIONS} of
|
||||||
As a result,
|
{\TSPLFOUR}.) As a result,
|
||||||
|
|
||||||
\schemedisplay
|
\schemedisplay
|
||||||
(begin
|
(begin
|
||||||
|
@ -85,7 +85,7 @@ and
|
||||||
|
|
||||||
both result in the giving \scheme{x} the value 3,
|
both result in the giving \scheme{x} the value 3,
|
||||||
even though an unbound variable reference to \scheme{a} would result if
|
even though an unbound variable reference to \scheme{a} would result if
|
||||||
the two forms within the latter \scheme{begin} expression where run
|
the two forms within the latter \scheme{begin} expression were run
|
||||||
independently at top level.
|
independently at top level.
|
||||||
|
|
||||||
Similarly, the \scheme{begin} form produced by a use of
|
Similarly, the \scheme{begin} form produced by a use of
|
||||||
|
@ -136,7 +136,7 @@ for internal variable definitions, for backward compatibility.
|
||||||
|
|
||||||
%----------------------------------------------------------------------------
|
%----------------------------------------------------------------------------
|
||||||
\noskipentryheader
|
\noskipentryheader
|
||||||
\formdef{define-values}{\categorysyntax}{(define-values formals \var{expr})}
|
\formdef{define-values}{\categorysyntax}{(define-values \var{formals} \var{expr})}
|
||||||
\listlibraries
|
\listlibraries
|
||||||
\endnoskipentryheader
|
\endnoskipentryheader
|
||||||
|
|
||||||
|
|
|
@ -310,7 +310,7 @@ predicate \scheme{transcoder?}, which should be standard but is not.
|
||||||
\scheme{little}.
|
\scheme{little}.
|
||||||
|
|
||||||
The codec returned by \scheme{utf-16-codec} can be used to create
|
The codec returned by \scheme{utf-16-codec} can be used to create
|
||||||
process data written UFT-16 format.
|
process data written UTF-16 format.
|
||||||
When called without the \var{endianness} argument or with \var{endianness}
|
When called without the \var{endianness} argument or with \var{endianness}
|
||||||
\scheme{big}, \scheme{utf-16-codec} returns a codec for standard UTF-16
|
\scheme{big}, \scheme{utf-16-codec} returns a codec for standard UTF-16
|
||||||
data, i.e., one that defaults to big-endian format if no byte-order mark
|
data, i.e., one that defaults to big-endian format if no byte-order mark
|
||||||
|
|
Loading…
Reference in New Issue
Block a user