tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Need hash: uthash?
Date: Thu, 28 Jul 2011 12:32:32 +0200	[thread overview]
Message-ID: <4E313AC0.2010106@bsd.lv> (raw)

Hi,

mandoc is getting a `tr' implementation*, needed primarily for perlpod. 
  This is expensive as it involves iterating over each character in each 
text string, then each element in an array of `tr' characters (or escape 
sequences).  Expect it in the next few commits (now it's in polish phase).

For the time being, this is implemented with the same linear search of 
the `ds' and `de' macro keys.  This means O(mn) performance over the 
number of words/characters (!) and keys.  In practise, when profiling 
the code, libroff spends a lot of time running through these lists. 
-mdoc gets away without even touching this code, but -man (especially 
perlpod) is smacked hard.

In short, the `ds', `de', and now `tr' macros can really benefit from a 
hash table.  I'm settling on using uthash** due to its license---I can 
directly include it in the code.  Does anybody have any better 
suggestions or criticism?  Interfacing with it is very easy and clean, 
and I've had some good performance benefits on heavy -man manuals (e.g., 
gcc, cvs, etc.).

Thanks,

Kristaps

*Search for `.tr': 
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man7/groff.7.html

**http://uthash.sourceforge.net/
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2011-07-28 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 10:32 Kristaps Dzonsons [this message]
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
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=4E313AC0.2010106@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).