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.

2 files changed, 5 insertions, 13 deletions

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  <rgm@gnu.org>
+
+        * cl.texi (Obsolete Setf Customization):
+        Move note on lack of setf functions to lispref/variables.texi.
+
 2012-11-03  Glenn Morris  <rgm@gnu.org>
 
         * 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