From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Le Wang <l26wang@gmail.com>
Cc: 9482-done@debbugs.gnu.org
Subject: bug#9482: specific manual text suggestion
Date: Fri, 16 Sep 2011 10:14:39 -0400 [thread overview]
Message-ID: <jwvhb4ctw3k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAM=K+ip2X0h4=jXd81V_O29_xrnJDObnJCe2hLhjS3Pwj94F=A@mail.gmail.com> (Le Wang's message of "Tue, 13 Sep 2011 21:25:28 +0800")
> 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)
{
prev parent reply other threads:[~2011-09-16 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 15:01 bug#9482: Documentation bug: Emacs Lisp Manual should say quoting does not cons explicitly in quoting section. related to bug#9469 Le Wang
2011-09-13 13:25 ` bug#9482: specific manual text suggestion Le Wang
2011-09-16 14:14 ` Stefan Monnier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvhb4ctw3k.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9482-done@debbugs.gnu.org \
--cc=l26wang@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.