On Tuesday 26 March 2002 09:04, Pietro Toniolo wrote:
Nay, I campiled the proposed program (every package on my side is in the
Last status) and, with -no-cygwin, I do have an unbuffered stdout.
You mean buffered?
Is it an undefined behavior of the c compiler?
But why a different default
Well, finally I figured out why the printf text is not displayed right away.
You need to turn off the tty switch in CYGWIN enviroment variable:
set CYGWIN=notty
(under DOS prompt, or in autoexec.bat), before starting the bash.
Wirawan
--
Unsubscribe info:
Hi,
Why does the screen output displayed using MSVC's printf subroutine not get
shown immediately under Cygwin shell (bash, specifically)? Rather, it would
wait for a long time before showing the text lines (many lines at once). How
to change this behavior?
I used the following (simple) code as
At 04:38 PM 3/25/2002, Wirawan Purwanto wrote:
Hi,
Why does the screen output displayed using MSVC's printf subroutine not get
shown immediately under Cygwin shell (bash, specifically)? Rather, it would
wait for a long time before showing the text lines (many lines at once). How
to change this
I have frequently seen unpredictable behavior of C prints in terms of their
timing. (I'm
an old guy and I still debug with prints from time to time). The only way I
got predictable
results was to do a buffer flush immediately after the print. In my case,
if I didn't do that,
and the program
Wirawan Purwanto wrote:
Why does the screen output displayed using MSVC's printf subroutine not get
shown immediately under Cygwin shell (bash, specifically)? Rather, it would
wait for a long time before showing the text lines (many lines at once). How
to change this behavior?
With
6 matches
Mail list logo
