From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: Need hash: uthash?
Date: Thu, 28 Jul 2011 17:04:01 +0200 [thread overview]
Message-ID: <20110728150401.GA6081@britannica.bec.de> (raw)
In-Reply-To: <4E313AC0.2010106@bsd.lv>
On Thu, Jul 28, 2011 at 12:32:32PM +0200, Kristaps Dzonsons wrote:
> 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).
Shouldn't this use a simple byte lookup table for the hot path?
Most of the tr processing applies to non-special sequences and unicode
or other \-literals are rare.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-07-28 15:04 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 [this message]
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=20110728150401.GA6081@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).