From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Qs on obarrays
Date: Wed, 12 Oct 2005 11:53:22 -0400 [thread overview]
Message-ID: <87wtki4tsl.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.10964.1129078391.20277.help-gnu-emacs@gnu.org
> Also, the obarray length must be supplied to make-vector. Anyone know a
> heuristic for a good vector length to use when you expect a certain number
> of symbols? I notice that the length of standard variable `obarray's value
> is 1511 (prime, presumably). If I expect on the order of N symbols, what is
> a good length to use? Or is there no simple formula? If not, anyone know a
> good length for, say, 100 symbols?
In most cases, you can advantageously use a hashtable instead of an obarray.
Those are automatically resized.
Stefan
next prev parent reply other threads:[~2005-10-12 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.10964.1129078391.20277.help-gnu-emacs@gnu.org>
2005-10-12 1:32 ` Qs on obarrays Pascal Bourguignon
2005-10-12 2:02 ` Drew Adams
2005-10-12 16:17 ` Kevin Rodgers
2005-10-12 17:14 ` Drew Adams
2005-10-12 18:23 ` Kevin Rodgers
2005-10-12 20:24 ` Drew Adams
2005-10-12 15:53 ` Stefan Monnier [this message]
2005-10-12 0:52 Drew Adams
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=87wtki4tsl.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).