From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: How to populate a property list?
Date: 30 Oct 2004 22:17:56 +0200 [thread overview]
Message-ID: <7evfcs3qq3.fsf@ada2.unipv.it> (raw)
In-Reply-To: 1tCdneLTFrxuSB7cRVn-pA@speakeasy.net
Hattuari <susudata@setidava.kushan.aa> writes:
> "[...] In contrast to association lists, the order of the pairs
> in the property list is not significant since the property names
> must be distinct."
this part of the elisp manual discusses plists in the abstract,
idealized sense. a little further on, where actual plist-munging
funcs are documented, there is some disclaimer about enforcement.
altogether, my understanding is that the elisp manual is not a
standards document, so its use of "must" et al are not rigorous.
when i read it, i expect the documentation describing the behavior
of functions and variables to be accurate; everything else is a
bonus, a hint of what hair and bondage lies outside the pleasant
island that is emacs and elisp programming.
of course, ymmv. you may wish for industrial strength building
materials instead of coconuts and sand castles. that's fine, too.
every once in a while some titanic technology grounds itself out
on the emacs shore -- in time, transformed by the incessant yap,
hap, lapping of the [yhl]acker s[eu]rf (itself a {t}id{al,le}
reflection of lunatic ellipsoid centered around "know" and "do"),
it becomes coconuts and sand castles in the playful hands of the
island inhabitants, as well.
thi
next prev parent reply other threads:[~2004-10-30 20:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 10:09 How to populate a property list? Hattuari
2004-10-26 12:28 ` Thien-Thi Nguyen
2004-10-27 20:38 ` Hattuari
2004-10-31 14:39 ` Kai Grossjohann
2004-10-26 15:24 ` Kevin Rodgers
2004-10-30 12:05 ` Hattuari
2004-10-30 17:12 ` Thien-Thi Nguyen
2004-10-30 17:54 ` Hattuari
2004-10-30 20:17 ` Thien-Thi Nguyen [this message]
2004-10-31 8:32 ` Hattuari
2004-10-31 8:57 ` Thien-Thi Nguyen
2004-10-31 15:23 ` Hattuari
2004-11-01 16:44 ` Kevin Rodgers
2004-10-31 14:36 ` Kai Grossjohann
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=7evfcs3qq3.fsf@ada2.unipv.it \
--to=ttn@glug.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.
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).