From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] libfmt port
Date: Mon, 27 Oct 2003 17:47:48 -0500 [thread overview]
Message-ID: <E1AEG9N-000FG9-Bm@t40.swtch.com> (raw)
In-Reply-To: Your message of "27 Oct 2003 19:26:54 EST." <20031028002654.18668.qmail@g.bio.cse.psu.edu>
> I really wish the libfmt port should use Plan 9 conventions for 'u',
> and not unix ones. I wouldn't be using it in the first place if I cared
> about unix compatability, especially when using or porting Plan 9 code!
>
> For example,
> libdraw/stringwidth.c:43: fprint(2, "stringwidth: bad character set for
> rune 0x%.4ux in %s\n", rune, name);
I believe the original intent was to match all the Unix semantics
so that Unix users could adopt it in their programs without needing
to learn the slight differences. I still think that's an admirable
goal.
What you want is a one-line change in fmt.c -- I even marked the line for you.
When I'm using libfmt as part of the Plan 9 porting environment,
I make the change.
Russ
prev parent reply other threads:[~2003-10-27 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 0:26 Scott Schwartz
2003-10-27 22:47 ` Russ Cox [this message]
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=E1AEG9N-000FG9-Bm@t40.swtch.com \
--to=rsc@swtch.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).