From: PT <mailshield.gg@mailnull.com>
Subject: Re: Structured data in Emacs Lisp
Date: Tue, 26 Apr 2005 19:21:06 +0200 [thread overview]
Message-ID: <op.spuntgy0p52o26@home-ca12fabbc0> (raw)
In-Reply-To: vfr7gxplsu.fsf@rpc71.cs.man.ac.uk
On Tue, 26 Apr 2005 18:03:45 +0200, Phillip Lord <p.lord@cs.man.ac.uk>
wrote:
>
> plists, or a hashtable would also work.
Are there any portability considerations regarding these constructs? Any
XEmacs guys here?
I develop on GNU Emacs, but I want to be on the safe side if the need of
supporting XEmacs arises in the future, so I'd avoid using GNU Emacs
specific data structures if possible.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
next prev parent reply other threads:[~2005-04-26 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 15:20 Structured data in Emacs Lisp PT
2005-04-26 15:28 ` Denis Bueno
[not found] ` <mailman.3069.1114529432.2895.help-gnu-emacs@gnu.org>
2005-04-26 15:57 ` PT
2005-04-26 16:59 ` Jim Ottaway
2005-04-27 5:35 ` Ian Zimmerman
2005-04-26 16:03 ` Phillip Lord
2005-04-26 17:21 ` PT [this message]
2005-04-27 11:13 ` Phillip Lord
2005-04-27 15:27 ` Klaus Berndl
2005-04-27 18:38 ` PT
2005-05-09 21:39 ` Christopher C. Stacy
2005-05-10 10:05 ` Phillip Lord
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=op.spuntgy0p52o26@home-ca12fabbc0 \
--to=mailshield.gg@mailnull.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.
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).