From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] hard-coded UTF-8 in wc.c
Date: Mon, 15 Mar 2010 18:44:41 -0400 [thread overview]
Message-ID: <8ce6a0712da68baec37593b11dce8e20@coraid.com> (raw)
In-Reply-To: <20100315213555.GA32333@machine>
On Mon Mar 15 17:46:11 EDT 2010, aim0shei@lavabit.com wrote:
> On Mon, Mar 15, 2010 at 05:13:40PM -0400, erik quanstrom wrote:
> > perhaps you have misunderstood.
> >
> > inside programs, sometimes unicode text is represented as
> > runes. runes are not sent over pipes nor stored in files.
> >
> > therefore, there is no need to wc runes.
>
> Yes, but why wc utility counts runes (wc(1) call them runes) manually
> using huge table instead of using functions from rune(3) such as utflen?
i didn't write wc, but i would imagine that it's for speed.
- erik
next prev parent reply other threads:[~2010-03-15 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 21:02 anonymous
2010-03-15 21:13 ` erik quanstrom
2010-03-15 21:35 ` anonymous
2010-03-15 22:44 ` erik quanstrom [this message]
2010-12-29 4:40 erik quanstrom
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=8ce6a0712da68baec37593b11dce8e20@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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).