[Emacs-diffs] Changes to emacs/man/cl.texi

[Werner LEMBERG]

Index: emacs/man/cl.texi
diff -c emacs/man/cl.texi:1.21 emacs/man/cl.texi:1.22
*** emacs/man/cl.texi:1.21      Sat May 29 15:51:23 2004
--- emacs/man/cl.texi   Fri Mar 25 10:17:33 2005
***************
*** 5,11 ****
  @copying
  This file documents the GNU Emacs Common Lisp emulation package.
  
! Copyright (C) 1993, 2002 Free Software Foundation, Inc.
  
  @quotation
  Permission is granted to copy, distribute and/or modify this document
--- 5,11 ----
  @copying
  This file documents the GNU Emacs Common Lisp emulation package.
  
! Copyright (C) 1993, 2002, 2005 Free Software Foundation, Inc.
  
  @quotation
  Permission is granted to copy, distribute and/or modify this document
***************
*** 991,997 ****
  @var{form}.
  
  The following Lisp forms will work as generalized variables, and
! so may legally appear in the @var{place} argument of @code{setf}:
  
  @itemize @bullet
  @item
--- 991,997 ----
  @var{form}.
  
  The following Lisp forms will work as generalized variables, and
! so may appear in the @var{place} argument of @code{setf}:
  
  @itemize @bullet
  @item
***************
*** 1073,1079 ****
  
  @item
  A call of the form @code{(substring @var{subplace} @var{n} address@hidden)},
! where @var{subplace} is itself a legal generalized variable whose
  current value is a string, and where the value stored is also a
  string.  The new string is spliced into the specified part of the
  destination string.  For example:
--- 1073,1079 ----
  
  @item
  A call of the form @code{(substring @var{subplace} @var{n} address@hidden)},
! where @var{subplace} is itself a valid generalized variable whose
  current value is a string, and where the value stored is also a
  string.  The new string is spliced into the specified part of the
  destination string.  For example:
***************
*** 2379,2385 ****
  
  The @code{by} value is always positive, even for downward-counting
  loops.  Some sort of @code{from} value is required for downward
! loops; @samp{for x downto 5} is not a legal loop clause all by
  itself.
  
  @item for @var{var} in @var{list} by @var{function}
--- 2379,2385 ----
  
  The @code{by} value is always positive, even for downward-counting
  loops.  Some sort of @code{from} value is required for downward
! loops; @samp{for x downto 5} is not a valid loop clause all by
  itself.
  
  @item for @var{var} in @var{list} by @var{function}
***************
*** 2481,2487 ****
  Due to a minor implementation restriction, it will not work to have
  more than one @code{for} clause iterating over symbols, hash tables,
  keymaps, overlays, or intervals in a given @code{loop}.  Fortunately,
! it would rarely if ever be useful to do so.  It @emph{is} legal to mix
  one of these types of clauses with other clauses like @code{for ... to}
  or @code{while}.
  
--- 2481,2487 ----
  Due to a minor implementation restriction, it will not work to have
  more than one @code{for} clause iterating over symbols, hash tables,
  keymaps, overlays, or intervals in a given @code{loop}.  Fortunately,
! it would rarely if ever be useful to do so.  It @emph{is} valid to mix
  one of these types of clauses with other clauses like @code{for ... to}
  or @code{while}.
  
***************
*** 2727,2733 ****
  explicit mechanism, such as @code{finally return}, to return
  the accumulated result.
  
! It is legal for several accumulation clauses of the same type to
  accumulate into the same place.  From Steele:
  
  @example
--- 2727,2733 ----
  explicit mechanism, such as @code{finally return}, to return
  the accumulated result.
  
! It is valid for several accumulation clauses of the same type to
  accumulate into the same place.  From Steele:
  
  @example
***************
*** 3248,3255 ****
  (get sym prop)  @equiv{}  (getf (symbol-plist sym) prop)
  @end example
  
! It is legal to use @code{getf} as a @code{setf} place, in which case
! its @var{place} argument must itself be a legal @code{setf} place.
  The @var{default} argument, if any, is ignored in this context.
  The effect is to change (via @code{setcar}) the value cell in the
  list that corresponds to @var{property}, or to cons a new property-value
--- 3248,3255 ----
  (get sym prop)  @equiv{}  (getf (symbol-plist sym) prop)
  @end example
  
! It is valid to use @code{getf} as a @code{setf} place, in which case
! its @var{place} argument must itself be a valid @code{setf} place.
  The @var{default} argument, if any, is ignored in this context.
  The effect is to change (via @code{setcar}) the value cell in the
  list that corresponds to @var{property}, or to cons a new property-value
***************
*** 3535,3541 ****
  integer; each different integer seed will result in a completely
  different sequence of random numbers.
  
! It is legal to print a @code{random-state} object to a buffer or
  file and later read it back with @code{read}.  If a program wishes
  to use a sequence of pseudo-random numbers which can be reproduced
  later for debugging, it can call @code{(make-random-state t)} to
--- 3535,3541 ----
  integer; each different integer seed will result in a completely
  different sequence of random numbers.
  
! It is valid to print a @code{random-state} object to a buffer or
  file and later read it back with @code{read}.  If a program wishes
  to use a sequence of pseudo-random numbers which can be reproduced
  later for debugging, it can call @code{(make-random-state t)} to
***************
*** 4575,4581 ****
  do not appear in the argument list are initialized based on the
  @var{default-value} in their slot descriptor.  Also, @code{&optional}
  and @code{&key} arguments which don't specify defaults take their
! defaults from the slot descriptor.  It is legal to include arguments
  which don't correspond to slot names; these are useful if they are
  referred to in the defaults for optional, keyword, or @code{&aux}
  arguments which @emph{do} correspond to slots.
--- 4575,4581 ----
  do not appear in the argument list are initialized based on the
  @var{default-value} in their slot descriptor.  Also, @code{&optional}
  and @code{&key} arguments which don't specify defaults take their
! defaults from the slot descriptor.  It is valid to include arguments
  which don't correspond to slot names; these are useful if they are
  referred to in the defaults for optional, keyword, or @code{&aux}
  arguments which @emph{do} correspond to slots.