delorie.com/archives/browse.cgi | search |
Date: | Sun, 1 Aug 1999 11:44:11 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Clemens Valens <c DOT valens AT mindless DOT com> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: Q: fprintf behaviour |
In-Reply-To: | <933002162.14440@www.remarq.com> |
Message-ID: | <Pine.SUN.3.91.990801114350.20304U-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Mon, 26 Jul 1999, Clemens Valens wrote: > It is like fprintf is printing to a buffer and only flushes it when > the loop finishes. Yes, fprintf buffers its output. Use fflush to force it to deliver buffered characters to the screen. > A 16-bit version of this program does not have this problem. DJGPP buffers more because writing the characters involves an expensive switch from protected mode to real mode (to call a DOS function). See section 9.4 of the FAQ, for more details.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |