Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!bellcore!tness7!tness1!sugar!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.unix.wizards
Subject: Re: Line Buffered output
Message-ID: <1718@ficc.uu.net>
Date: 5 Oct 88 13:54:44 GMT
References: <411@marob.MASA.COM> <178@arnold.UUCP> <3442@crash.cts.com> <13866@mimsy.UUCP>
Organization: SCADA
Lines: 19

In article <13866@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) writes:
> 	main() { putchar('g'); putchar('o'); putchar('\n'); for (;;); }

> 2BSD and 4BSD will both print `go\n' if stdout is a terminal, while
> under what I think you were proposing, you would never see anything.

I wouldn't expect to see anything in this program. I'm a good boy and
always fflush() when I know I'm going to be going away for a while.
Do you bother to fflush() before a fork()? Why not?

Oh well, I suppose you have good reasons for what you do. I just wish
you'd let me turn it off so I can really cook.

How does this all interact with curses, which generates newlines
essentially at random? Flushes at the newline and then an explicit
flush when update completes?
-- 
Peter da Silva  `-_-'  Ferranti International Controls Corporation.
"Have you hugged  U  your wolf today?"            peter@ficc.uu.net