From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>
Subject: Re: [PATCH] implement .rm
Date: Tue, 11 Jan 2011 00:47:58 +0100 [thread overview]
Message-ID: <4D2B9AAE.60708@bsd.lv> (raw)
In-Reply-To: <20110110234131.GB4964@iris.usta.de>
> Thus, i will believe this gives us a measureable improvement
> when i see the measurement!
>
> Using hash tables (or RB-trees?) probably makes sense, but please
> try to not hack up a third (or fourth? i have lost count)
> independent hash table implementation in mandoc. ;-)
Ingo,
You've a point in this. It's true that all roff, mdoc, and man name
lookups generally have 1-3 letters. Let me look into a nice, unified
interface for hashing these. If it saves space and speed, I'll float a
patch for review.
Thanks,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-01-10 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 22:52 [PATCH] uniform parsing of names in libroff Ingo Schwarze
2011-01-10 23:10 ` Kristaps Dzonsons
2011-01-10 23:41 ` [PATCH] implement .rm Ingo Schwarze
2011-01-10 23:47 ` Kristaps Dzonsons [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=4D2B9AAE.60708@bsd.lv \
--to=kristaps@bsd.lv \
--cc=schwarze@usta.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).