9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] APE printf difference
Date: Mon,  7 Jul 2008 00:04:39 +0100	[thread overview]
Message-ID: <a7d531a84f842f26980f8cefd1623a11@terzarima.net> (raw)
In-Reply-To: <78b8a6f4e03e55b062b5f7ab8a09484f@quanstro.net>

>i don't see a requirment to flush stdout or any other output stream in c99 ...

"As initially opened, the standard error stream is not fully buffered; the standard input and standard
output streams are fully buffered if and only if the stream can be determined not to refer
to an interactive device."

but "can be determined" is perhaps a weasel phrase. it's probably expected that the system can tell
the difference, but isatty() is a bit devious in the plan 9 world. more serious is that APE could face either way.
if it's trying to help portability in, it should have as many functions as possible, and those quite generous.
if it's trying to help portability out, it should be strict and emphasise all the little pockets of "undefined behaviour" or
"implementation-defined" behaviour, to get you to spell things out. if that's the case (and i think that's the design) you need the fflush.
if the former, you'd perhaps want _IOLBF if isatty(1) is true.




  reply	other threads:[~2008-07-06 23:04 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 [this message]
2008-07-07 21:01     ` Pietro Gagliardi
2008-07-07 21:21       ` erik quanstrom
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=a7d531a84f842f26980f8cefd1623a11@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).