From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: Need hash: uthash?
Date: Sun, 31 Jul 2011 13:29:00 +0200 [thread overview]
Message-ID: <20110731112900.GA2434@britannica.bec.de> (raw)
In-Reply-To: <20110731104223.GB1831@iris.usta.de>
On Sun, Jul 31, 2011 at 12:42:23PM +0200, Ingo Schwarze wrote:
> The first things we will be asked is: Why not use the existing
> tools? If i understand correctly, uthash is a dynamic hasher
> (as opposed to a perfect static hasher). What about hash(3) in
> /usr/src/lib/libc/db/hash/ ? Is that useable?
The db(3) interface is crap. It's easier to just write a small hash
table from scratch, especially with a good hash function.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-07-31 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 10:32 Kristaps Dzonsons
2011-07-28 15:04 ` Joerg Sonnenberger
2011-07-28 15:12 ` Kristaps Dzonsons
2011-07-28 15:18 ` Joerg Sonnenberger
2011-07-28 19:14 ` Kristaps Dzonsons
2011-07-31 10:42 ` Ingo Schwarze
2011-07-31 11:29 ` Joerg Sonnenberger [this message]
2011-07-31 12:00 ` Kristaps Dzonsons
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=20110731112900.GA2434@britannica.bec.de \
--to=joerg@britannica.bec.de \
--cc=tech@mdocml.bsd.lv \
/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).