summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Kastrup <dak@gnu.org>2011-10-28 17:52:42 +0200
committerDavid Kastrup <dak@gnu.org>2014-08-27 22:54:55 +0200
commit3eb00210e96180234b4459d797a411148d954374 (patch)
tree44c82c6e41b55ee69c3d6b9ecb3347062b05beec
parent48678617b169957433c562612151f2a71be50b59 (diff)
Issue 4071: scheme-tutorial.itely: missing closing paren
But it turns out that the "formal" definition of a list given there is unsuitable for determining the list status of circular lists because the definition, well, turns out to be circular.
-rw-r--r--Documentation/extending/scheme-tutorial.itely7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/extending/scheme-tutorial.itely b/Documentation/extending/scheme-tutorial.itely
index 7503306b1f..fc2eba1c6d 100644
--- a/Documentation/extending/scheme-tutorial.itely
+++ b/Documentation/extending/scheme-tutorial.itely
@@ -275,9 +275,10 @@ Abelson, see
@node Lists
@unnumberedsubsubsec Lists
-A very common Scheme data structure is the @emph{list}. Formally, a
-list is defined as either the empty list (represented as @code{'()},
-or a pair whose @code{cdr} is a list.
+A very common Scheme data structure is the @emph{list}. Formally,
+a @q{proper} list is defined to be either the empty list with its
+input form @code{'()} and length@tie{}0, or a pair whose
+@code{cdr} in turn is a shorter list.
There are many ways of creating lists. Perhaps the most common is
with the @code{list} procedure: