emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lispref/lists.texi


From: Richard M . Stallman
Subject: [Emacs-diffs] Changes to emacs/lispref/lists.texi
Date: Mon, 14 Feb 2005 05:14:29 -0500

Index: emacs/lispref/lists.texi
diff -c emacs/lispref/lists.texi:1.47 emacs/lispref/lists.texi:1.48
*** emacs/lispref/lists.texi:1.47       Wed Jun 23 16:27:49 2004
--- emacs/lispref/lists.texi    Mon Feb 14 10:14:29 2005
***************
*** 86,185 ****
    The @sc{cdr} of any nonempty list @var{l} is a list containing all the
  elements of @var{l} except the first.
  
- @node Lists as Boxes
- @comment  node-name,  next,  previous,  up
- @section Lists as Linked Pairs of Boxes
- @cindex box representation for lists
- @cindex lists represented as boxes
- @cindex cons cell as box
- 
-   A cons cell can be illustrated as a pair of boxes.  The first box
- represents the @sc{car} and the second box represents the @sc{cdr}.
- Here is an illustration of the two-element list, @code{(tulip lily)},
- made from two cons cells:
- 
- @example
- @group
-  ---------------         ---------------
- | car   | cdr   |       | car   | cdr   |
- | tulip |   o---------->| lily  |  nil  |
- |       |       |       |       |       |
-  ---------------         ---------------
- @end group
- @end example
- 
-   Each pair of boxes represents a cons cell.  Each box ``refers to'',
- ``points to'' or ``holds'' a Lisp object.  (These terms are
- synonymous.)  The first box, which describes the @sc{car} of the first
- cons cell, contains the symbol @code{tulip}.  The arrow from the
- @sc{cdr} box of the first cons cell to the second cons cell indicates
- that the @sc{cdr} of the first cons cell is the second cons cell.
- 
-   The same list can be illustrated in a different sort of box notation
- like this:
- 
- @example
- @group
-     --- ---      --- ---
-    |   |   |--> |   |   |--> nil
-     --- ---      --- ---
-      |            |
-      |            |
-       --> tulip    --> lily
- @end group
- @end example
- 
-   Here is a more complex illustration, showing the three-element list,
- @code{((pine needles) oak maple)}, the first element of which is a
- two-element list:
- 
- @example
- @group
-     --- ---      --- ---      --- ---
-    |   |   |--> |   |   |--> |   |   |--> nil
-     --- ---      --- ---      --- ---
-      |            |            |
-      |            |            |
-      |             --> oak      --> maple
-      |
-      |     --- ---      --- ---
-       --> |   |   |--> |   |   |--> nil
-            --- ---      --- ---
-             |            |
-             |            |
-              --> pine     --> needles
- @end group
- @end example
- 
-   The same list represented in the first box notation looks like this:
- 
- @example
- @group
-  --------------       --------------       --------------
- | car   | cdr  |     | car   | cdr  |     | car   | cdr  |
- |   o   |   o------->| oak   |   o------->| maple |  nil |
- |   |   |      |     |       |      |     |       |      |
-  -- | ---------       --------------       --------------
-     |
-     |
-     |        --------------       ----------------
-     |       | car   | cdr  |     | car     | cdr  |
-      ------>| pine  |   o------->| needles |  nil |
-             |       |      |     |         |      |
-              --------------       ----------------
- @end group
- @end example
- 
    @xref{Cons Cell Type}, for the read and print syntax of cons cells and
  lists, and for more ``box and arrow'' illustrations of lists.
  
  @node List-related Predicates
  @section Predicates on Lists
  
!   The following predicates test whether a Lisp object is an atom, is a
! cons cell or is a list, or whether it is the distinguished object
! @code{nil}.  (Many of these predicates can be defined in terms of the
! others, but they are used so often that it is worth having all of them.)
  
  @defun consp object
  This function returns @code{t} if @var{object} is a cons cell, @code{nil}
--- 86,102 ----
    The @sc{cdr} of any nonempty list @var{l} is a list containing all the
  elements of @var{l} except the first.
  
    @xref{Cons Cell Type}, for the read and print syntax of cons cells and
  lists, and for more ``box and arrow'' illustrations of lists.
  
  @node List-related Predicates
  @section Predicates on Lists
  
!   The following predicates test whether a Lisp object is an atom,
! whether it is a cons cell or is a list, or whether it is the
! distinguished object @code{nil}.  (Many of these predicates can be
! defined in terms of the others, but they are used so often that it is
! worth having all of them.)
  
  @defun consp object
  This function returns @code{t} if @var{object} is a cons cell, @code{nil}
***************
*** 749,757 ****
  incrementing by @var{separation}, and ending at or just before
  @var{to}.  @var{separation} can be positive or negative and defaults
  to 1.  If @var{to} is @code{nil} or numerically equal to @var{from},
! the one element list @code{(from)} is returned.  If @var{separation}
! is 0 and @var{to} is neither @code{nil} nor numerically equal to
! @var{from}, an error is signaled.
  
  All arguments can be integers or floating point numbers.  However,
  floating point arguments can be tricky, because floating point
--- 666,679 ----
  incrementing by @var{separation}, and ending at or just before
  @var{to}.  @var{separation} can be positive or negative and defaults
  to 1.  If @var{to} is @code{nil} or numerically equal to @var{from},
! the value is the one-element list @code{(@var{from})}.  If @var{to} is
! less than @var{from} with a positive @var{separation}, or greater than
! @var{from} with a negative @var{separation}, the value is @code{nil}
! because those arguments specify an empty sequence.
! 
! If @var{separation} is 0 and @var{to} is neither @code{nil} nor
! numerically equal to @var{from}, @code{number-sequence} signals an
! error, since those arguments specify an infinite sequence.
  
  All arguments can be integers or floating point numbers.  However,
  floating point arguments can be tricky, because floating point




reply via email to

[Prev in Thread] Current Thread [Next in Thread]