From: Phillip Lord <p.lord@cs.man.ac.uk>
Subject: Re: Structured data in Emacs Lisp
Date: 27 Apr 2005 12:13:19 +0100 [thread overview]
Message-ID: <vffyxch3qo.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: op.spuntgy0p52o26@home-ca12fabbc0
>>>>> "PT" == PT <mailshield.gg@mailnull.com> writes:
PT> On Tue, 26 Apr 2005 18:03:45 +0200, Phillip Lord
PT> <p.lord@cs.man.ac.uk>
PT> wrote:
>>
>> plists, or a hashtable would also work.
PT> Are there any portability considerations regarding these
PT> constructs? Any XEmacs guys here?
plist should work fine I think. hashtables were new for Emacs 21. But
I've used them in packages which apparently work on XEmacs, so you
should be alright.
PT> I develop on GNU Emacs, but I want to be on the safe side if the
PT> need of supporting XEmacs arises in the future, so I'd avoid
PT> using GNU Emacs specific data structures if possible.
Sensible enough. My experience with trying to support both emacs is
that it's often small differences which cause problems rather than
missing features. For one package I wrote, I spent an hour trying to
debug an XEmacs problem which turned out to be because the `subseq'
function behaves differently between the two. What a nightmare!
In general, now, I write for GNU Emacs. If it's a nice package,
someone will port it to XEmacs sooner or later.
Cheers
Phil
next prev parent reply other threads:[~2005-04-27 11:13 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
2005-04-27 11:13 ` Phillip Lord [this message]
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=vffyxch3qo.fsf@rpc71.cs.man.ac.uk \
--to=p.lord@cs.man.ac.uk \
/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).