commit 2f3a977b58fe7e8f7cce32179e6b8bf2997279b5 parent b5a9d3ed72619f7162e7dfc2f07b0da53b7b4047 Author: Wolfgang Corcoran-Mathe <wcm@sigwinch.xyz> Date: Sat, 3 Feb 2024 14:21:33 -0500 Use subscript vars. macros. Diffstat:
| M | doc/r7rs-small/procedures/pairs-and-lists.texinfo | | | 4 | ++-- |
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/r7rs-small/procedures/pairs-and-lists.texinfo b/doc/r7rs-small/procedures/pairs-and-lists.texinfo @@ -38,8 +38,8 @@ The above definitions imply that all lists have finite length and are terminated by the empty list. The most general notation (external representation) for Scheme pairs is -the ``dotted'' notation @code{(}@var{c@sub{1}}@code{ . }@var{c@sub{2}}@code{)} where -@var{c@sub{1}} is the value of the car field and @var{c@sub{2}} is the value of the +the ``dotted'' notation @code{(}@vari{c}@code{ . }@varii{c}@code{)} where +@vari{c} is the value of the car field and @varii{c} is the value of the cdr field. For example @code{(4 . 5)} is a pair whose car is 4 and whose cdr is 5. Note that @code{(4 . 5)} is the external representation of a pair, not an expression that evaluates to a pair.