r7rs-small-texinfo

Unnamed repository; edit this file 'description' to name the repository.
git clone https://kaka.farm/~git/r7rs-small-texinfo
Log | Files | Refs | README

commit 62f82a8840896770ad411249f743c2a5c802d247
parent 812b250271e30dd7e253d3b268e3c1c94720f0c1
Author: Wolfgang Corcoran-Mathe <wcm@sigwinch.xyz>
Date:   Wed,  7 Feb 2024 12:41:56 -0500

Intro etc.: Correct report names.

Diffstat:
Mdoc/r7rs-small/r7rs-small.texinfo | 24++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/doc/r7rs-small/r7rs-small.texinfo b/doc/r7rs-small/r7rs-small.texinfo @@ -15,7 +15,7 @@ @titlepage @title Scheme -@subtitle Revised7 Report on the Algorithmic Language Scheme +@subtitle Revised@sup{7} Report on the Algorithmic Language Scheme ALEX SHINN, JOHN COWAN, AND ARTHUR A. GLECKLER (Editors) @@ -32,10 +32,10 @@ EMMANUEL MEDERNACH BENJAMIN L. RUSSEL RICHARD KELSEY, WILLIAM CLINGER, AND JONATHAN REES -(Editors, Revised5 Report on the Algorithmic Language Scheme) +(Editors, Revised@sup{5} Report on the Algorithmic Language Scheme) MICHAEL SPERBER, R. KENT DYBVIG, MATTHEW FLATT, AND ANTON VAN STRAATEN -(Editors, Revised6 Report on the Algorithmic Language Scheme) +(Editors, Revised@sup{6} Report on the Algorithmic Language Scheme) Dedicated to the memory of John McCarthy and Daniel Weinreb @@ -77,9 +77,9 @@ syntax and semantics. The report concludes with a list of references and an alphabetic index. -Note: The editors of the R5RS and R6RS reports are listed as authors of this report in +Note: The editors of the @rfivers{} and @rsixrs{} reports are listed as authors of this report in recognition of the substantial portions of this report that are copied directly from -R5RS and R6RS. There is no intended implication that those editors, individually or +@rfivers{} and @rsixrs{}. There is no intended implication that those editors, individually or collectively, support or do not support this report. @menu @@ -143,23 +143,23 @@ Their report, the RRRS [@ref{RRRS}], was published at MIT and Indiana University the spring of 1988 resulted in R4RS [@ref{R4RS}], which became the basis for the IEEE Standard for the Scheme Programming Language in 1991 [@ref{IEEEScheme}]. In 1998, several additions to the IEEE standard, including high-level hygienic macros, multiple return values, and eval, were -finalized as the R5RS [@ref{R5RS}]. +finalized as the @rfivers{} [@ref{@rfivers{}}]. In the fall of 2006, work began on a more ambitious standard, including many new improvements and stricter requirements made in the interest of improved portability. The -resulting standard, the R6RS, was completed in August 2007 [@ref{R6RS}], and was organized as a +resulting standard, the @rsixrs{}, was completed in August 2007 [@ref{@rsixrs{}}], and was organized as a core language and set of mandatory standard libraries. Several new implementations of -Scheme conforming to it were created. However, most existing R5RS implementations -(even excluding those which are essentially unmaintained) did not adopt R6RS, or adopted +Scheme conforming to it were created. However, most existing @rfivers{} implementations +(even excluding those which are essentially unmaintained) did not adopt @rsixrs{}, or adopted only selected parts of it. In consequence, the Scheme Steering Committee decided in August 2009 to divide the standard into two separate but compatible languages---a ``small'' language, suitable for -educators, researchers, and users of embedded languages, focused on R5RS +educators, researchers, and users of embedded languages, focused on @rfivers{} compatibility, and a ``large'' language focused on the practical needs of mainstream -software development, intended to become a replacement for R6RS. The present report +software development, intended to become a replacement for @rsixrs{}. The present report describes the ``small'' language of that effort: therefore it cannot be considered in -isolation as the successor to R6RS. +isolation as the successor to @rsixrs{}. We intend this report to belong to the entire Scheme community, and so we grant permission to copy it in whole or in part without fee. In particular, we encourage