From:	"Campbell, Rolf [SKY:1U32:EXCH]" <cp1v45 AT americasm01 DOT nt DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Q: fprintf behaviour
Date:	Mon, 26 Jul 1999 11:34:28 -0400
Organization:	Nortel Networks
Lines:	16
Message-ID:	<379C8004.ABA25972@americasm01.nt.com>
References:	<933002162 DOT 14440 AT www DOT remarq DOT com>
NNTP-Posting-Host:	bmerhc00.ca.nortel.com
Mime-Version:	1.0
X-Mailer:	Mozilla 4.6 [en] (X11; I; HP-UX B.10.20 9000/712)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Clemens Valens wrote:

> It is like
> fprintf is printing to a buffer and only flushes it when
> the loop finishes. A 16-bit version of this program does
> not have this problem.

    This is exactly what it does.  If you had read the FAQ, it would have told
you that DJGPP (as well as just about every other 32-bit compiler) uses
buffered i/o.  You can use "fflush(stdout)" to flush the output stream.

--
     -Rolf Campbell (39)3-6318

- Raw text -