From: Rob Pike rob@plan9.bell-labs.com
Subject: [9fans] fprint(int fd, const char* format,...);
Date: Fri, 21 Nov 1997 11:01:35 -0500 [thread overview]
Message-ID: <19971121160135.I-_cY8ZOdW8e7kWhLHbF-7Dk5MU2sgj6dh13ecnCIyY@z> (raw)
Not that it matters much, but I'm pretty sure that the 'print'
library was done as part of an emulation library for writing
Plan 9-like tools. That style of print (c.f. printf) started around
here when Andrew Hume wrote a new buffered I/O library for
Version 8 Unix. The style continued through a couple of more
libraries and found its way into Plan 9.
-rob
next reply other threads:[~1997-11-21 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-21 16:01 Rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-11-21 18:33 Tom
1997-11-21 18:27 Scott
1997-11-21 16:18 Boyd
1997-11-21 15:51 erik
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=19971121160135.I-_cY8ZOdW8e7kWhLHbF-7Dk5MU2sgj6dh13ecnCIyY@z \
--to=9fans@9fans.net \
/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).