commit b7a012800c4d13411055cea5e1ea4913db10601b
parent ca9bd70bec41fdcfe61ac09f110a32b39b7bf92e
Author: Wolfgang Corcoran-Mathe <wcm@sigwinch.xyz>
Date: Wed, 7 Feb 2024 12:31:19 -0500
Summary & Intro: Citations.
Diffstat:
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/doc/r7rs-small/r7rs-small.texinfo b/doc/r7rs-small/r7rs-small.texinfo
@@ -50,7 +50,7 @@ December 19, 2022
The report gives a defining description of the programming language Scheme. Scheme is
a statically scoped and properly tail recursive dialect of the Lisp programming language
-[23] invented by Guy Lewis Steele Jr. and Gerald Jay Sussman. It was designed to have
+[@ref{McCarthy}] invented by Guy Lewis Steele Jr. and Gerald Jay Sussman. It was designed to have
exceptionally clear and simple semantics and few different ways to form expressions. A
wide variety of programming paradigms, including imperative, functional, and
object-oriented styles, find convenient expression in Scheme.
@@ -126,27 +126,28 @@ in a consistent and reliable manner.
@heading Background
-The first description of Scheme was written in 1975 [35]. A revised report [31] appeared in
+The first description of Scheme was written in 1975 [@ref{Scheme75}]. A revised report [@ref{Scheme78}] appeared in
1978, which described the evolution of the language as its MIT implementation was
-upgraded to support an innovative compiler [32]. Three distinct projects began in 1981
-and 1982 to use variants of Scheme for courses at MIT, Yale, and Indiana University [27,
-24, 14]. An introductory computer science textbook using Scheme was published in 1984
-[1].
+upgraded to support an innovative compiler [@ref{Rabbit}]. Three distinct projects began in 1981
+and 1982 to use variants of Scheme for courses at MIT, Yale, and Indiana University
+[@ref{Rees82}, @ref{MITScheme}, @ref{Scheme311}]
+An introductory computer science textbook using Scheme was published in 1984
+[@ref{SICP}].
As Scheme became more widespread, local dialects began to diverge until students and
researchers occasionally found it difficult to understand code written at other sites.
Fifteen representatives of the major implementations of Scheme therefore met in
October 1984 to work toward a better and more widely accepted standard for Scheme.
-Their report, the RRRS [8], was published at MIT and Indiana University in the summer of
-1985. Further revision took place in the spring of 1986, resulting in the R3RS [29]. Work in
-the spring of 1988 resulted in R4RS [10], which became the basis for the IEEE Standard for
-the Scheme Programming Language in 1991 [18]. In 1998, several additions to the IEEE
+Their report, the RRRS [@ref{RRRS}], was published at MIT and Indiana University in the summer of
+1985. Further revision took place in the spring of 1986, resulting in the R3RS [@ref{R3RS}]. Work in
+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 [20].
+finalized as the R5RS [@ref{R5RS}].
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 [33], and was organized as a
+resulting standard, the R6RS, was completed in August 2007 [@ref{R6RS}], 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
@@ -197,9 +198,9 @@ John Ramsdell, Guillermo Rozas, Mike Shaff, Jonathan Shapiro, Guy Steele, Julie
Perry Wagle, Mitchel Wand, Daniel Weise, Henry Wu, and Ozan Yigit. We thank Carol
Fessenden, Daniel Friedman, and Christopher Haynes for permission to use text from the
Scheme 311 version 4 reference manual. We thank Texas Instruments, Inc. for permission
-to use text from the TI Scheme Language Reference Manual [37]. We gladly acknowledge the
-influence of manuals for MIT Scheme [24], T [28], Scheme 84 [15], Common Lisp [34], and
-Algol 60 [25], as well as the following SRFIs: 0, 1, 4, 6, 9, 11, 13, 16, 30, 34, 39, 43, 46, 62, and
+to use text from the TI Scheme Language Reference Manual [@ref{TImanual85}]. We gladly acknowledge the
+influence of manuals for MIT Scheme [@ref{MITScheme}], T [@ref{Rees84}], Scheme 84 [@ref{Scheme84}], Common Lisp [@ref{CLtL}], and
+Algol 60 [@ref{Naur63}], as well as the following SRFIs: 0, 1, 4, 6, 9, 11, 13, 16, 30, 34, 39, 43, 46, 62, and
87, all of which are available at http://srfi.schemers.org.
@include overview.texinfo
