From: Adam Brown <adambrown1 AT geocities DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Display question...
Date: Sun, 30 Aug 1998 00:44:43 +0200
Organization: IP Worldcom
Lines: 17
Message-ID: <35E8845B.27B0@geocities.com>
References: <3 DOT 0 DOT 5 DOT 16 DOT 19980827002417 DOT 0cbf3f84 AT mail DOT tir DOT com>
Reply-To: adambrown1 AT geocities DOT com
NNTP-Posting-Host: portls84.worldcom.ch
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Thomas J. Hruska wrote:
> 
> I'm new to this mailing list (but I'm on about 8 others, so it's nothing
> really new to me how things work).  Anyway, I have a problem with the
> printf command.  When I do something like:
> 
>   printf("Hello World!");
> 
> It won't print anything to the screen until either the program is finished
> or until a newline character is printed.  I never had this problem with my
> Borland compiler (16-bit only).  What is the difference?  I read some of
> the online documentation at delorie.com and nothing came up about
> compiler/library differences.  Is this a bug, or am I missing something?

This is because DJGPP was programmed with a bloody-minded adherence to
the ANSI C standard, which states that the printf buffer does not need
to be flushed at the end of the call.