From: arnold@skeeve.com
To: robpike@gmail.com, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Foreign-Language UNIX Efforts
Date: Mon, 20 Mar 2023 05:02:36 -0600 [thread overview]
Message-ID: <202303201102.32KB2a13018306@freefriends.org> (raw)
In-Reply-To: <CAKzdPgwkaUO-i64_OL0Oy=eRcTp52Rm96zw3yzN38SszPD7-=A@mail.gmail.com>
Looking at the current man pages, the interfaces are very simple, which is
fine. Do you think they would have worked for character sets with
shift states and such?
Thanks,
Arnold
Rob Pike <robpike@gmail.com> wrote:
> Exactly the way we did it in Plan 9, and published in the paper cited
> earlier. In fact, it's possible the library work was done as early as 1989,
> but I'm not sure. Certainly by 1990.
>
> -rob
>
>
> On Mon, Mar 20, 2023 at 6:55 PM <arnold@skeeve.com> wrote:
>
> > Hi Rob.
> >
> > Rob Pike <robpike@gmail.com> wrote:
> >
> > > (Speaking of design by committee, the multibyte stuff in C89 was
> > atrocious,
> > > and I heard was done in committee to get someone, perhaps the Japanese,
> > to
> > > sign off.)
> >
> > It's not lovely, but I wouldn't call it atrocious. It gets the job
> > done; code using it can handle multibyte encodings while being totally
> > character-set agnostic. I speak from experience, gawk does this.
> > (I use the "restartable" routins - mbrlen() and so on.)
> >
> > I understand that Unicode + UTF-8 solve the issue completely. But I'd
> > like to ask, in all seriousness and so that I can learn, given the world
> > as it was in 1989, how would you solve the problem? If you had designed
> > the C level routines, what would they have looked like?
> >
> > Thanks,
> >
> > Arnold
> >
next prev parent reply other threads:[~2023-03-20 11:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 5:00 [TUHS] " segaloco via TUHS
2023-03-19 13:32 ` [TUHS] " Diomidis Spinellis
2023-03-19 13:47 ` [TUHS] " Ralph Corderoy
2023-03-19 20:27 ` [TUHS] " Rob Pike
2023-03-20 7:55 ` arnold
2023-03-20 9:22 ` Rob Pike
2023-03-20 11:02 ` arnold [this message]
2023-03-20 15:44 ` Steffen Nurpmeso
2023-03-20 22:01 ` John Cowan
2023-03-20 22:28 ` Steffen Nurpmeso
2023-03-22 2:25 ` Larry McVoy
2023-03-22 2:52 ` Rob Pike
2023-03-22 7:12 ` Mehdi Sadeghi via TUHS
2023-03-22 7:33 ` Rob Pike
2023-03-22 7:40 ` arnold
2023-03-22 10:02 ` Skip Tavakkolian
2023-03-22 10:09 ` Skip Tavakkolian
2023-03-22 12:02 ` Rob Pike
2023-03-22 22:33 ` Steffen Nurpmeso
2023-03-22 23:33 ` segaloco via TUHS
2023-03-23 0:01 ` Warren Toomey via TUHS
2023-03-19 13:38 ` Edouard Klein
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=202303201102.32KB2a13018306@freefriends.org \
--to=arnold@skeeve.com \
--cc=robpike@gmail.com \
--cc=tuhs@tuhs.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 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).