From: Dave Love <d.love@dl.ac.uk>
Subject: Re: Idea: Use of gethash/puthash for GNU Emacs 21?
Date: 01 Sep 2001 17:37:22 +0100 [thread overview]
Message-ID: <rzqofouzx31.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <m37kvzdb4l.fsf@quimbies.gnus.org>
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> I mean, it just uses `intern', and since one of the most central
LMI> parts of Emacs is symbol lookup, it's bound to be pretty
LMI> optimized...
The performance of interning probably has room for improvement, though
as far as I remember, the ...hash functions use the same algorithm and
parameters.
The salient feature of hash tables in Gnus is that various code
depends on them being obarrays, since it uses `read' to intern into
them. That said, the Gnus functions should still be used
consistently, rather than explicitly creating obarrays in various
places.
prev parent reply other threads:[~2001-09-01 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 7:10 Christoph Conrad
2001-06-02 8:23 ` Christoph Conrad
2001-08-19 20:54 ` Lars Magne Ingebrigtsen
2001-09-01 16:37 ` Dave Love [this message]
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=rzqofouzx31.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.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 NNTP newsgroup(s).