From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: Is it safe to modify a property list directly with PLIST-PUT?
Date: Sun, 26 Jul 2009 22:07:36 +0200 [thread overview]
Message-ID: <87zlargqd3.fsf@galatea.local> (raw)
In-Reply-To: 87ab2rs8kv.fsf@iki.fi
Teemu Likonen <tlikonen@iki.fi> writes:
> I use a list of property lists to store data. It's like this:
>
> (setq my-data '((:foo "one" :bar "two")
> (:foo "three" :bar "four")))
It is never safe to modify literal data!
(setq my-data (list (list :foo "one" :bar "two")
(list :foo "three" :bar "four")))
or:
(setq my-data (copy-tree '((:foo "one" :bar "two")
(:foo "three" :bar "four"))))
> Sometimes I need to modify the data and a command like this seems to
> work:
>
> (plist-put (nth 1 my-data) :bar "New value")
>
> That is, PLIST-PUT modifies the property list and variable MY-DATA
> contains now the modified list:
>
> ((:foo "one" :bar "two")
> (:foo "three" :bar "New value"))
>
> The question: Is this reliable? Is it guaranteed that it will always
> modify the list correctly? If not, how would you suggest doing it
> instead?
It is safe, as long as the property list is not literal data (that
must be considered immutable).
Notice also that like delete, plist-put returns the result, it cannot
always modify the property list in place. So you have to restore the
result:
(setf (nth 1 my-data) (plist-put (nth 1 my-data) :bar "New value"))
> Common Lisp has so nice SETF macro...
Of course, emacs has it too:
(require 'cl) ; put that in your ~/.emacs
--
__Pascal Bourguignon__
next prev parent reply other threads:[~2009-07-26 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 16:38 Is it safe to modify a property list directly with PLIST-PUT? Teemu Likonen
2009-07-26 16:58 ` Teemu Likonen
2009-07-26 17:51 ` Lennart Borgman
2009-07-26 20:07 ` Pascal J. Bourguignon [this message]
2009-07-27 5:59 ` Teemu Likonen
2009-07-27 8:31 ` Pascal J. Bourguignon
2009-07-27 17:45 ` Teemu Likonen
2009-07-27 20:17 ` Pascal J. Bourguignon
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=87zlargqd3.fsf@galatea.local \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@gnu.org \
/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.