From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] u9fs and va_copy()
Date: Thu, 16 Sep 2004 08:24:40 -0700 [thread overview]
Message-ID: <7359f049040916082450e10591@mail.gmail.com> (raw)
In-Reply-To: <b44864ca97531a92bcddd4d2083c278e@plan9.bell-labs.com>
Yes, you should do this. It's a royal pain, though. The fmt library needs
a hell of a lot of work to be compliant. I've done it but I don't like the code
and plan to redo it sometime soon. I also have implementations of the
POSIX %4$d stuff and %'d stuff, with plans for %'f. Joy.
I'll ship it back when I'm done, but it will be a while; I have other fires at
the moment.
-rob
next prev parent reply other threads:[~2004-09-16 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:49 jmk
2004-09-16 15:24 ` Rob Pike [this message]
2004-09-20 9:02 Aharon Robbins
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=7359f049040916082450e10591@mail.gmail.com \
--to=robpike@gmail.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).