GNU bug report logs - #9482
Documentation bug: Emacs Lisp Manual should say quoting does not cons explicitly in quoting section. related to bug#9469

Previous Next

Full log

Message #13 received at 9482-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Le Wang <l26wang <at> gmail.com>
Cc: 9482-done <at> debbugs.gnu.org
Subject: Re: specific manual text suggestion
Date: Fri, 16 Sep 2011 10:14:39 -0400

> My terminology may be not quite right, but if I read something like
> this, the difference would be much clearer.

Thanks for your sample text.  I tweaked it a bit to make it hopefully
even more explicit, see patch below.


        Stefan


--- src/eval.c	2011-09-09 01:06:52 +0000
+++ src/eval.c	2011-09-16 14:09:39 +0000
@@ -475,6 +475,14 @@
 
 DEFUN ("quote", Fquote, Squote, 1, UNEVALLED, 0,
        doc: /* Return the argument, without evaluating it.  `(quote x)' yields `x'.
+Warning: `quote' does not construct its return value, but just returns
+the value that was pre-constructed by the Lisp reader (see info node
+`(elisp)Printed Representation').
+This means that '(a . b) is not identical to (cons 'a 'b): the former
+does not cons.  Quoting should be reserved for constants that will
+never be modified by side-effects, unless you like self-modifying
+code.  See the common pitfall in info node `(elisp)Rearrangement' for
+an example of unexpected results when a quoted object is modified.
 usage: (quote ARG)  */)
   (Lisp_Object args)
 {

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.