This is the mail archive of the
mailing list for the Cygwin project.
Re: [Patch] cygcheck: eprintf + display_error: Do /something/.
On Dec 17 09:46, Bas van Gompel wrote:
> Op Fri, 17 Dec 2004 01:19:32 -0500 schreef Christopher Faylor
> in <20041217061932.GH26712@trixie.casa.cgf.cx>:
> : On Fri, Dec 17, 2004 at 04:33:10AM +0100, Bas van Gompel wrote:
> : > * cygcheck.cc (eprintf): Flush stdout before, and stderr after output,
> : > when stdout and stderr both don't refer to ttys.
> : > (display_error): Use eprintf.
> : Ok. I don't see any reason to check for ttyness, then. If this is an issue
> : then lets just flush stdout prior to doing anything with stderr. Flushing
> : stderr should always be a no-op.
> It isn't (a no-op). (See the snippet in my previous mail.) Is this a
> difference between cygwin and mingw, maybe?
Hmm, if stderr is not unbuffered in mingw, then that should be fixed
in mingw, shouldn't it?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:firstname.lastname@example.org
Red Hat, Inc.