From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] APE printf difference
Date: Mon, 7 Jul 2008 17:21:37 -0400 [thread overview]
Message-ID: <fb803b997d5392e937d5bf797dc41df4@coraid.com> (raw)
In-Reply-To: <6ACC80E1-EB30-44AF-A1CA-72B990AE6A6B@mac.com>
> So there you go. I don't know about C99, but I do know POSIX/SUS are
> designed to be aligned with standard C.
i think you're missing the bit where determining what
an interactive device is is not straightfoward, as forsyth
pointed out. think of connecting to a shell on the other
end of a unix socket. or #|.
if you really depend on the prompt being synchronous,
you'd better either use nonbuffered io or fflush before prompting.
this all is a good argument for plan 9's decoupling of the print
library from the buffered i/o library.
- erik
next prev parent reply other threads:[~2008-07-07 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 22:03 Fernan Bolando
2008-07-06 22:14 ` erik quanstrom
2008-07-06 23:04 ` Charles Forsyth
2008-07-07 21:01 ` Pietro Gagliardi
2008-07-07 21:21 ` erik quanstrom [this message]
2008-07-07 23:02 ` Charles Forsyth
2008-07-08 0:07 ` a
2008-07-09 11:12 ` lucio
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=fb803b997d5392e937d5bf797dc41df4@coraid.com \
--to=quanstro@coraid.com \
--cc=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).