From 651af8c6316d7fca5b3dadb52b596c2485b2c5d3 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Mon, 5 Nov 2012 21:03:34 -0500 Subject: [PATCH] Move note on lack of setf functions from cl.texi to lispref * doc/lispref/variables.texi (Adding Generalized Variables): Move note on lack of setf functions to here... * doc/misc/cl.texi (Obsolete Setf Customization): ... from here. --- doc/lispref/ChangeLog | 2 ++ doc/lispref/variables.texi | 11 +++++++++++ doc/misc/ChangeLog | 5 +++++ doc/misc/cl.texi | 13 ------------- 4 files changed, 18 insertions(+), 13 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index d97a258da34..c588e81dd1f 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -3,6 +3,8 @@ * variables.texi (Setting Generalized Variables): Split most of previous contents into this subsection. (Adding Generalized Variables): New subsection. + Move note on lack of setf functions here from misc/cl.texi. + * elisp.texi: Add Generalized Variables subsections to detailed menu. 2012-11-05 Chong Yidong diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi index f9f69850ef8..c1a18a81bc1 100644 --- a/doc/lispref/variables.texi +++ b/doc/lispref/variables.texi @@ -2119,3 +2119,14 @@ value that was set. An example of using this macro is: This is the most general way to define a new @code{setf} expansion. @end defmac @end ignore + +@cindex CL note---no @code{setf} functions +Common Lisp defines another way to specify the @code{setf} behavior of +a function, namely ``@code{setf} functions'', whose names are lists +@code{(setf @var{name})} rather than symbols. For example, +@code{(defun (setf foo) @dots{})} defines the function that is used +when @code{setf} is applied to @code{foo}. Emacs does not support +this. It is a compile-time error to use @code{setf} on a form that +has not already had an appropriate expansion defined. In Common Lisp, +this is not an error since the function @code{(setf @var{func})} might +be defined later. diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog index 62308037fec..c182cb04b6c 100644 --- a/doc/misc/ChangeLog +++ b/doc/misc/ChangeLog @@ -1,3 +1,8 @@ +2012-11-06 Glenn Morris + + * cl.texi (Obsolete Setf Customization): + Move note on lack of setf functions to lispref/variables.texi. + 2012-11-03 Glenn Morris * cl.texi: Further general copyedits. diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi index e182c2600f9..a8cc2e47406 100644 --- a/doc/misc/cl.texi +++ b/doc/misc/cl.texi @@ -5105,19 +5105,6 @@ See also the source code for the setf-method for simpler case, then massaging the result. @end defun -@c FIXME does not belong here any more, maybe in lispref? -Modern Common Lisp defines a second, independent way to specify -the @code{setf} behavior of a function, namely ``@code{setf} -functions'' whose names are lists @code{(setf @var{name})} -rather than symbols. For example, @code{(defun (setf foo) @dots{})} -defines the function that is used when @code{setf} is applied to -@code{foo}. This package does not currently support @code{setf} -functions. In particular, it is a compile-time error to use -@code{setf} on a form which has not already been @code{defsetf}'d -or otherwise declared; in newer Common Lisps, this would not be -an error since the function @code{(setf @var{func})} might be -defined later. - @node GNU Free Documentation License @appendix GNU Free Documentation License -- 2.39.5