Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!emory!ogicse!oregon!jmeissen
From: jmeissen@oregon.oacis.org ( Staff OACIS)
Newsgroups: comp.sys.amiga
Subject: Re: program question, stdin, stdout.
Message-ID: <577@oregon.oacis.org>
Date: 1 Aug 90 21:05:28 GMT
References: <2033@bnlux0.bnl.gov> <573@oregon.oacis.org> <7N6$5X*@masalla.fulcrum.bt.co.uk>
Organization: Oregon Advanced Computing Institute (OACIS), Beaverton, OR
Lines: 22

In article <7N6$5X*@masalla.fulcrum.bt.co.uk> S.J.Raybould@fulcrum.bt.co.uk (Simon Raybould) writes:
 >In article <573@oregon.oacis.org> jmeissen@oregon.oacis.org ( Staff OACIS) writes:
 >>flushed. printf() gets around this problem by calling fflush() each time it gets called.
 >
 >RUBBISH!!! printf() doesn't call fflush() each time it is called. The above
 >example works because there is a newline at the end which WILL cause printf()
 >to flush the stdio buffer. printf() uses stdio and will flush the same as all
 >other stdio functions i.e. when the buffer is full or a forwarding condition
 >is met such as \n.

If you please, I'm the one who put the fflush call into the printf function in the
Lattice C library. I think I know what I'm talking about.


 >
 >SJR
 >
-- 
John Meissen .............................. Oregon Advanced Computing Institute
jmeissen@oacis.org        (Internet) | "That's the remarkable thing about life;
..!sequent!oacis!jmeissen (UUCP)     |  things are never so bad that they can't
jmeissen                  (BIX)      |  get worse." - Calvin & Hobbes