Date: Fri, 21 Nov 1997 21:01:14 -0800 (PST)
Message-Id: <199711220501.VAA16015@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Cesar Scarpini Rabak <csrabak AT dce03 DOT ipt DOT br>,
        Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: stdout flushing after printf, SIGALRM signal and GNU Make
Precedence: bulk

At 08:56  11/19/1997 -0200, Cesar Scarpini Rabak wrote:
>At 09:00 19/11/97 +0100, Thomas Demmer wrote:
>
>>That should be explained in the FAQ, or check the libc info
>>files for the magic word setvbuf.
>>Anyway, because this is the most frequently asked frequently
>>asked question, DJ is planning to change stdout to unbuffered.
>                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
>>
>>Seems to be too much UNIXism in a DOS world. 
>
>Just my two cents:
>
>If this is being considered, might we have then some sort of flag which
>allow the programmer to choose between buffered or not?
IMHO, this already exists: it's called `setvbuf'. :) If your program
depended on line buffering (a bad idea anyway), or if you want full
buffering for performance, it should be simple to insert the relevant
`setvbuf' call at the top of `main'; certainly at least as simple as setting
a flag.

Nate Eldredge
eldredge AT ap DOT net