All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Beginnings of conpat 32 code cleanups
Date: 22 Nov 2002 12:38:55 -0800	[thread overview]
Message-ID: <arm4kv$bsl$1@cesium.transmeta.com> (raw)
In-Reply-To: 20021122131351.C30808@duath.fsmlabs.com

Followup to:  <20021122131351.C30808@duath.fsmlabs.com>
By author:    Cort Dougan <cort@fsmlabs.com>
In newsgroup: linux.dev.kernel
> 
> Plan9 takes it a step further and tackles the char/8-byte issue.  A
> printable character is a 16-byte entity - a rune - while char is an 8-byte
> quantity.  Doing everything in UNICODE forced the issue, I think.
> 

... at which point it promptly fell apart as 16-bit Unicode was very
quickly found to be insufficient (not really surprising since the
16-bit decision was based on technical convenience rather than actual
requirements.)

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-11-22 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22  5:23 [PATCH] Beginnings of conpat 32 code cleanups Stephen Rothwell
2002-11-22 19:47 ` Linus Torvalds
2002-11-22 19:54   ` Larry McVoy
2002-11-22 20:13     ` Cort Dougan
2002-11-22 20:38       ` H. Peter Anvin [this message]
2002-11-23  0:28   ` Stephen Rothwell
2002-11-25 19:48     ` Linus Torvalds
2002-11-23  5:16   ` Anton Blanchard
2002-11-25 20:00     ` Linus Torvalds
2002-11-26 13:53 ` Pavel Machek

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='arm4kv$bsl$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.