unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Geoff Gole" <geoffgole@gmail.com>
To: "Peter Mao" <peter.mao@gmail.com>, 1734@emacsbugs.donarmstrong.com
Subject: bug#1734: a bug in elisp?
Date: Tue, 30 Dec 2008 15:39:31 +0900	[thread overview]
Message-ID: <f5bc73230812292239x39b24148t192eb6a4f97c76c6@mail.gmail.com> (raw)

This is normal. The list structure constructed by '(0) is conceptually
constant in the function, but remains mutable and is not protected in
any way. When you destructively modify it with nconc, the 'constant'
will change.

The solution: don't do that.






             reply	other threads:[~2008-12-30  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  6:39 Geoff Gole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-30  5:44 bug#1734: a bug in elisp? Peter Mao

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5bc73230812292239x39b24148t192eb6a4f97c76c6@mail.gmail.com \
    --to=geoffgole@gmail.com \
    --cc=1734@emacsbugs.donarmstrong.com \
    --cc=peter.mao@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).