Merge pull request #308 from owaddell/owaddell/typos

fix a couple typos and some duplicate words in csug
original commit: 92b49b413ddaecda347570a6b30290fc5f46172f
This commit is contained in:
Andy Keep 2018-05-22 21:49:12 -04:00 committed by GitHub
commit 364413fda8
10 changed files with 14 additions and 14 deletions

View File

@ -23,7 +23,7 @@ Section~\ref{SECTCOMPATEXTENDSYNTAX}
describes \scheme{extend-syntax} macros. describes \scheme{extend-syntax} macros.
These features are supported directly by current versions of {\ChezScheme}, These features are supported directly by current versions of {\ChezScheme},
but support may be dropped in future versions. but support may be dropped in future versions.
New programs should use the standard mechanisms described in New programs should use the standard mechanisms described
in \emph{The Scheme Programming Language, 4th Edition}~\cite{Dybvig:tspl4} in \emph{The Scheme Programming Language, 4th Edition}~\cite{Dybvig:tspl4}
instead. instead.

View File

@ -287,7 +287,7 @@ The first form is identical to the Revised$^6$ Report \scheme{dynamic-wind}.
When the optional \var{critical?} argument is present and non-false, When the optional \var{critical?} argument is present and non-false,
the \var{in} thunk is invoked in a critical section along with the code the \var{in} thunk is invoked in a critical section along with the code
that records that the body has been entered, and the \var{out} thunk is that records that the body has been entered, and the \var{out} thunk is
invoked in a critical section section along with the code that records invoked in a critical section along with the code that records
that the body has been exited. that the body has been exited.
Extreme caution must be taken with this form of \scheme{dynamic-wind}, Extreme caution must be taken with this form of \scheme{dynamic-wind},
since an error or long-running computation can leave interrupts since an error or long-running computation can leave interrupts

View File

@ -444,7 +444,7 @@ year = 1995}
author = {Oscar Waddell and Dipanwita Sarkar and R. Kent Dybvig}, author = {Oscar Waddell and Dipanwita Sarkar and R. Kent Dybvig},
title = {Fixing Letrec: A Faithful Yet Efficient Implementation of {Scheme}'s title = {Fixing Letrec: A Faithful Yet Efficient Implementation of {Scheme}'s
Recursive Binding Construct}, Recursive Binding Construct},
journal = {Higher-order and and symbolic computation}, journal = {Higher-order and symbolic computation},
volume = 18, volume = 18,
number = "3/4", number = "3/4",
pages = {299--326}, pages = {299--326},

View File

@ -120,7 +120,7 @@ Its default value is \scheme{100}.
\endentryheader \endentryheader
The value of \scheme{ee-default-repeat} is a nonnegative fixnum The value of \scheme{ee-default-repeat} is a nonnegative fixnum
value that determines the number of of times the next command is value that determines the number of times the next command is
repeated after the \scheme{ee-command-repeat} editing command repeated after the \scheme{ee-command-repeat} editing command
(bound to \scheme{Esc-^U} by default) is used and \emph{not} (bound to \scheme{Esc-^U} by default) is used and \emph{not}
followed by a sequence of digits. followed by a sequence of digits.

View File

@ -3485,7 +3485,7 @@ A thread created via the Scheme procedure \scheme{fork-thread} starts
in the active state and need not be activated. in the active state and need not be activated.
Any thread that has been deactivated, and any Any thread that has been deactivated, and any
thread created by some mechanism other than \scheme{fork-thread} must, thread created by some mechanism other than \scheme{fork-thread} must,
however, be activated before before it can access Scheme data or execute however, be activated before it can access Scheme data or execute
Scheme code. A foreign callable that is declared with \scheme{__collect_safe} Scheme code. A foreign callable that is declared with \scheme{__collect_safe}
can activate a calling thread. can activate a calling thread.
Otherwise, \scheme{Sactivate_thread} must be used to activate a thread. Otherwise, \scheme{Sactivate_thread} must be used to activate a thread.

View File

@ -131,7 +131,7 @@ valid identifiers in {\ChezScheme}.
Second, the single-character sequences \scheme{\schlbrace} and Second, the single-character sequences \scheme{\schlbrace} and
\scheme{\schrbrace} are identifiers. \scheme{\schrbrace} are identifiers.
Third, identifiers containing arbitrary characters may be printed by Third, identifiers containing arbitrary characters may be printed by
escaping them them with \scheme{\} or with \scheme{|}. escaping them with \scheme{\} or with \scheme{|}.
\scheme{\} is used to escape a single character (except 'x', since \scheme{\} is used to escape a single character (except 'x', since
\scheme{\x} marks the start of a hex scalar value), \scheme{\x} marks the start of a hex scalar value),
whereas \scheme{|} is used whereas \scheme{|} is used
@ -139,7 +139,7 @@ to escape the group of characters that follow it up through the
matching \scheme{|}. matching \scheme{|}.
For example, \scheme{\||\|} is an identifier with a two-character For example, \scheme{\||\|} is an identifier with a two-character
name consisting of the character \scheme{|} followed by the name consisting of the character \scheme{|} followed by the
the character \scheme{\}, and \scheme{|hit me!|} is an identifier whose name character \scheme{\}, and \scheme{|hit me!|} is an identifier whose name
contains a space. contains a space.
In addition, gensyms (page~\ref{desc:gensym}) are printed with In addition, gensyms (page~\ref{desc:gensym}) are printed with

View File

@ -670,7 +670,7 @@ message.
\endentryheader \endentryheader
\noindent \noindent
When When \var{obj} is \scheme{#f}, the port's beginning-of-line (BOL) When \var{obj} is \scheme{#f}, the port's beginning-of-line (BOL)
flag is cleared; otherwise, the port's BOL flag is set. flag is cleared; otherwise, the port's BOL flag is set.
The BOL flag is consulted by \scheme{fresh-line} The BOL flag is consulted by \scheme{fresh-line}
@ -2555,7 +2555,7 @@ objects \scheme{\var{obj} \dots}.
Characters are copied from \var{format-string} to the output string from Characters are copied from \var{format-string} to the output string from
left to right, until \var{format-string} is exhausted. left to right, until \var{format-string} is exhausted.
The format string may contain one or more \var{format directives}, which are The format string may contain one or more \var{format directives}, which are
multi-character sequences prefixed by a a tilde (~\scheme{~}~). multi-character sequences prefixed by a tilde (~\scheme{~}~).
Each directive is replaced by some other text, often involving one or more Each directive is replaced by some other text, often involving one or more
of the \scheme{\var{obj} \dots} arguments, as determined by the semantics of the \scheme{\var{obj} \dots} arguments, as determined by the semantics
of the directive. of the directive.

View File

@ -1317,7 +1317,7 @@ be parsed as a number.
\item \item
A symbol whose name contains arbitrary characters may be written by A symbol whose name contains arbitrary characters may be written by
escaping them them with \scheme{\} or with \scheme{|}. escaping them with \scheme{\} or with \scheme{|}.
\scheme{\} is used to escape a single character (except 'x', since \scheme{\} is used to escape a single character (except 'x', since
\scheme{\x} marks the start of a hex scalar value), \scheme{\x} marks the start of a hex scalar value),
whereas \scheme{|} is used whereas \scheme{|} is used

View File

@ -1835,7 +1835,7 @@ If instead this file were compiled, using \scheme{compile-file}, the
compiler would arrange to define \scheme{mvlet} before continuing compiler would arrange to define \scheme{mvlet} before continuing
with the expansion and evaluation of the \scheme{mvlet} expression, with the expansion and evaluation of the \scheme{mvlet} expression,
but it would not arrange to define \scheme{nodups?}. but it would not arrange to define \scheme{nodups?}.
Thus the expansion of the \scheme{mvlet} expression would fails. Thus the expansion of the \scheme{mvlet} expression would fail.
In this case it does not help to evaluate the syntactic extension alone. In this case it does not help to evaluate the syntactic extension alone.
A solution in this case would be to move the definition of A solution in this case would be to move the definition of
@ -4362,7 +4362,7 @@ in bytes, including not only the bytes occupied for Scheme objects
but also various forms of overhead, including fragmentation and but also various forms of overhead, including fragmentation and
reserved but not currently occupied memory, and is thus an accurate reserved but not currently occupied memory, and is thus an accurate
measure of the amount of heap memory currently reserved from the measure of the amount of heap memory currently reserved from the
the operating system for the current process. operating system for the current process.
%---------------------------------------------------------------------------- %----------------------------------------------------------------------------
\entryheader \entryheader

View File

@ -1655,7 +1655,7 @@ The application installation script should install {\PetiteChezScheme}
if not already installed on the target system. if not already installed on the target system.
It should install the application boot file in the same directory as It should install the application boot file in the same directory as
the {\PetiteChezScheme} boot file petite.boot is installed, the {\PetiteChezScheme} boot file petite.boot is installed,
and it should should install the application shared libraries, if any, and it should install the application shared libraries, if any,
either in the same location or in a standard location for shared libraries either in the same location or in a standard location for shared libraries
on the target system. on the target system.
It should also create a link to or copy of the {\PetiteChezScheme} It should also create a link to or copy of the {\PetiteChezScheme}
@ -1757,7 +1757,7 @@ parameter (Section~\ref{SECTUSEINTERACTION}).
Most of the options are described elsewhere in this chapter, and a few Most of the options are described elsewhere in this chapter, and a few
are self-explanatory. are self-explanatory.
The remainder pertain the loading of boot files at system start-up The remainder pertain to the loading of boot files at system start-up
time and are described below. time and are described below.
\index{boot files}% \index{boot files}%