scsh-conservatory
/
scsh-0.6
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

\R4RS is not a valid LaTeX macro name. 

Besides, we're at R5RS now.
This commit is contained in:
sperber 2002-01-07 13:26:32 +00:00
parent 737917e695
commit b2bcc730ad
7 changed files with 204 additions and 204 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/scsh-manual/decls.tex
View File

@ -12,7 +12,7 @@
\def\Unix{{Unix}} % Not smallcaps, according to Bart. \def\Unix{{Unix}} % Not smallcaps, according to Bart.
\def\Scheme{{Scheme}} \def\Scheme{{Scheme}}
\def\scm{{Scheme 48}} \def\scm{{Scheme 48}}
\def\R4RS{R4RS} \def\RnRS{R5RS}
\def\Posix{\textsc{Posix}} \def\Posix{\textsc{Posix}}
\def\sharpf{\normalfont\texttt{\#f}} \def\sharpf{\normalfont\texttt{\#f}}

4
doc/scsh-manual/intro.tex
View File

@ -214,11 +214,11 @@ and so forth.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Lexical issues} \section{Lexical issues}
Scsh's lexical syntax is just {\R4RS} {\Scheme}, with the following Scsh's lexical syntax is just {\RnRS} {\Scheme}, with the following
exceptions. exceptions.
\subsection{Extended symbol syntax} \subsection{Extended symbol syntax}
Scsh's symbol syntax differs from {\R4RS} {\Scheme} in the following ways: Scsh's symbol syntax differs from {\RnRS} {\Scheme} in the following ways:
\begin{itemize} \begin{itemize}
\item In scsh, symbol case is preserved by \ex{read} and is significant on \item In scsh, symbol case is preserved by \ex{read} and is significant on
symbol comparison. This means symbol comparison. This means

2
doc/scsh-manual/miscprocs.tex
View File

@ -27,7 +27,7 @@ the second element is \ex{(nth \var{list} 1)}, and so on.
This procedure is provided as it is useful for accessing elements This procedure is provided as it is useful for accessing elements
from the lists returned by the field-readers (chapter~\ref{chapt:fr-awk}). from the lists returned by the field-readers (chapter~\ref{chapt:fr-awk}).
The functionality of \ex{nth} is equivalent to that of \R4RS{}'s The functionality of \ex{nth} is equivalent to that of \RnRS{}'s
\ex{list-ref}. Therefore, \ex{nth} will go away in a future release. \ex{list-ref}. Therefore, \ex{nth} will go away in a future release.
\end{desc} \end{desc}

2
doc/scsh-manual/procnotation.tex
View File

@ -174,7 +174,7 @@ in the child process before executing the body of the form.
This guarantees that the \ex{begin} form, like all other process forms, This guarantees that the \ex{begin} form, like all other process forms,
``sees'' the effects of any associated I/O redirections. ``sees'' the effects of any associated I/O redirections.
Note that {\R4RS} does not specify whether or not \ex{|} and \ex{|+} Note that {\RnRS} does not specify whether or not \ex{|} and \ex{|+}
are readable symbols. Scsh does. are readable symbols. Scsh does.
\section{Using extended process forms in \Scheme} \section{Using extended process forms in \Scheme}

2
doc/scsh-manual/running.tex
View File

@ -6,7 +6,7 @@
Scsh is currently implemented on top of {\scm}, a freely-available Scsh is currently implemented on top of {\scm}, a freely-available
{\Scheme} implementation written by Jonathan Rees and Richard Kelsey. {\Scheme} implementation written by Jonathan Rees and Richard Kelsey.
{\scm} uses a byte-code interpreter for good code density, portability {\scm} uses a byte-code interpreter for good code density, portability
and medium efficiency. It is {\R4RS}. and medium efficiency. It is {\RnRS}.
It also has a module system designed by Jonathan Rees. It also has a module system designed by Jonathan Rees.
Scsh's design is not {\scm} specific, although the current implementation Scsh's design is not {\scm} specific, although the current implementation

10
doc/scsh-manual/syscalls.tex
View File

@ -131,8 +131,8 @@ This can be overridden if the programmer wishes.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{I/O} \section{I/O}
\subsection{Standard {\R4RS} I/O procedures} \subsection{Standard {\RnRS} I/O procedures}
In scsh, most standard {\R4RS} i/o operations (such as \ex{display} or In scsh, most standard {\RnRS} i/o operations (such as \ex{display} or
\ex{read-char}) work on both integer file descriptors and {\Scheme} ports. \ex{read-char}) work on both integer file descriptors and {\Scheme} ports.
When doing i/o with a file descriptor, the i/o operation is done When doing i/o with a file descriptor, the i/o operation is done
directly on the file, bypassing any buffered data that may have directly on the file, bypassing any buffered data that may have
@ -141,7 +141,7 @@ Note that character-at-a-time operations such as \ex{read-char}
are likely to be quite slow when performed directly upon file are likely to be quite slow when performed directly upon file
descriptors. descriptors.
The standard {\R4RS} procedures \ex{read-char}, \ex{char-ready?}, \ex{write}, The standard {\RnRS} procedures \ex{read-char}, \ex{char-ready?}, \ex{write},
\ex{display}, \ex{newline}, \ex{display}, \ex{newline},
and \ex{write-char} are all generic, accepting integer file descriptor and \ex{write-char} are all generic, accepting integer file descriptor
arguments as well as ports. arguments as well as ports.
@ -590,7 +590,7 @@ this is dependent on the OS implementation.
\ex{open/read+write} flags. \ex{open/read+write} flags.
% %
The returned port is an input port if the \var{flags} permit it, The returned port is an input port if the \var{flags} permit it,
otherwise an output port. \R4RS/\scm/scsh do not have input/output ports, otherwise an output port. \RnRS/\scm/scsh do not have input/output ports,
so it's one or the other. This should be fixed. (You can hack simultaneous so it's one or the other. This should be fixed. (You can hack simultaneous
i/o on a file by opening it r/w, taking the result input port, i/o on a file by opening it r/w, taking the result input port,
and duping it to an output port with \ex{dup->outport}.) and duping it to an output port with \ex{dup->outport}.)
@ -606,7 +606,7 @@ this is dependent on the OS implementation.
\codex{(bitwise-ior open/create open/truncate)} \codex{(bitwise-ior open/create open/truncate)}
for \ex{open-output-file}. for \ex{open-output-file}.
These defaults make the procedures backwards-compatible with their These defaults make the procedures backwards-compatible with their
unary {\R4RS} definitions. unary {\RnRS} definitions.
\end{defundescx} \end{defundescx}
\begin{defundesc} {open-fdes} {fname flags [perms]} \integer \begin{defundesc} {open-fdes} {fname flags [perms]} \integer

2
doc/scsh-manual/tty.tex
View File

@ -337,7 +337,7 @@ the terminal to be opened for both input and output.
The port returned is an input port if the \var{flags} permit it, The port returned is an input port if the \var{flags} permit it,
otherwise an output port. otherwise an output port.
\R4RS/\scm/scsh do not have input/output ports, \RnRS/\scm/scsh do not have input/output ports,
so it's one or the other. so it's one or the other.
However, you can get both read and write ports open on a terminal However, you can get both read and write ports open on a terminal
by opening it read/write, taking the result input port, by opening it read/write, taking the result input port,