* [9fans] libfmt port
@ 2003-10-28 0:26 Scott Schwartz
2003-10-27 22:47 ` Russ Cox
0 siblings, 1 reply; 2+ messages in thread
From: Scott Schwartz @ 2003-10-28 0:26 UTC (permalink / raw)
To: 9fans
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);
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9fans] libfmt port
2003-10-28 0:26 [9fans] libfmt port Scott Schwartz
@ 2003-10-27 22:47 ` Russ Cox
0 siblings, 0 replies; 2+ messages in thread
From: Russ Cox @ 2003-10-27 22:47 UTC (permalink / raw)
To: 9fans
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-10-28 0:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-28 0:26 [9fans] libfmt port Scott Schwartz
2003-10-27 22:47 ` Russ Cox
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).