From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ... in the Kingdom of Sources
Date: Tue, 9 Sep 2003 08:50:35 -0700 [thread overview]
Message-ID: <60daeacb70b35a962967fe444d298342@mightycheese.com> (raw)
In-Reply-To: <JOCdnUa8OfYQlsCiXTWJhA@comcast.com>
> Since an encoding error should "never" occur, we thought it
> better to stop scanning rather that plow ahead and convert some
> unknown amount of garbage once synchronization has been lost.
> It was also not evident that there would always be a "spare"
> wide-character code available for in-band signaling.
experience tells that 'never' happens many times a day. for most
tools, let's say, oh, a terminal program, cat, grep, web browser, ...,
you should most certainly plow ahead. for the few programs that
absolutely must not make mistakes, it's still possible to discover an
error has occurred (error rune + only one byte consumed). the point -
often lost on standards committees - is that convenience is often more
important than universality or rigidity.
i admit that our strategy is tied to utf-8.
-rob
next prev parent reply other threads:[~2003-09-09 15:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 11:54 David Presotto
2003-09-05 12:14 ` Lucio De Re
2003-09-05 12:33 ` boyd, rounin
2003-09-07 9:00 ` Aharon Robbins
2003-09-07 9:05 ` boyd, rounin
2003-09-08 9:10 ` Douglas A. Gwyn
2003-09-08 9:52 ` boyd, rounin
2003-09-08 17:33 ` rob pike, esq.
2003-09-09 8:34 ` Douglas A. Gwyn
2003-09-09 15:50 ` rob pike, esq.
2003-09-09 15:50 ` rob pike, esq. [this message]
2003-09-10 10:17 ` Bruce Ellis
2003-09-11 9:07 ` Douglas A. Gwyn
2003-09-11 13:06 ` rog
2003-09-11 14:01 ` Lucio De Re
2003-09-11 14:25 ` rog
2003-09-11 15:17 ` Lucio De Re
2003-09-12 9:18 ` Douglas A. Gwyn
2003-09-11 15:48 ` rob pike, esq.
2003-09-11 17:04 ` Lucio De Re
2003-09-11 17:40 ` chris
2003-09-12 4:13 ` boyd, rounin
2003-09-12 9:18 ` Douglas A. Gwyn
2003-09-12 15:18 ` rob pike, esq.
2003-09-12 16:39 ` rog
2003-09-12 9:18 ` Douglas A. Gwyn
2003-09-12 0:56 ` Bruce Ellis
2003-09-11 15:42 ` rob pike, esq.
2003-09-12 1:18 ` okamoto
2003-09-12 9:18 ` Ralph Corderoy
2003-09-12 9:57 ` Bruce Ellis
2003-09-15 8:27 ` Douglas A. Gwyn
2003-09-12 3:53 ` boyd, rounin
2003-09-12 3:01 ` Dan Cross
2003-09-07 13:48 ` Russ Cox
2003-09-07 15:45 ` David Presotto
2003-09-06 11:13 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 12:04 David Presotto
2003-09-05 6:39 lucio
2003-09-05 6:31 ` Lucio De Re
2003-09-05 11:30 ` David Presotto
2003-09-05 11:42 ` David Presotto
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=60daeacb70b35a962967fe444d298342@mightycheese.com \
--to=rob@mightycheese.com \
--cc=9fans@cse.psu.edu \
/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).