Re: Buffered IO curiosity effects non-CYGWIN programs.

[Andrej Borsenkow <Andrej dot Borsenkow at mow dot siemens dot ru>]

On Tue, 24 Jul 2001, Ed Bradford wrote:

> There were no replys to my question about buffered IO.
>
> Write a 14 line program reading lines from stdin and printing them to
> stdout. Compile with Microsoft CL.exe. Run the program from bash and it
> runs as if buffering were turned on. It doesn't recognize the console as an
> interactive output requiring immediate flushing. Run the very same program
> from cmd.exe and it works correctly.
>
> This is a bug in something because it effects programs that are not
> compiled with CYGWIN. Has anyone seen this problem and is there any type of
> resolution?
>

It is very interesting definition of "bug". "Bug" is when program behaves
differently as designed. Nobody ever claimed that Cygwin was designed to
transparently run Win32 applications.

Cygwin terminal is not Win32 console. I do not know if it is somewhere in
FAQ (cannot check at this moment) but it probably should be.

There is a program from Egor Duda that may help, it is called ttyfier.
Search archives. I have not tried it myself.

-andrej




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/