This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] cygcheck: eprintf + display_error: Do /something/.


On Fri, Dec 17, 2004 at 03:51:47AM +0100, Bas van Gompel wrote:
>Op Thu, 16 Dec 2004 21:02:05 -0500 schreef Christopher Faylor
>in <20041217020205.GA26712@trixie.casa.cgf.cx>:
>:  On Fri, Dec 17, 2004 at 02:04:40AM +0100, Buzz wrote:
>: > Here is another attempt at making eprintf a usable/used function in
>: > cygcheck. It this time just flushes stdout and stderr before/after
>: > output on stderr, when both (stdout and stderr) are ttys.
>
>[...]
>
>:  I'm still not sure what you're hoping to accomplish with this.  I haven't
>:  seen any problems with flushing in cygcheck and I wouldn't expect any
>:  since the flushing should be automatic if stdout is a "tty".
>
>I seem to be making a mess here... The point is to have the error-messages
>appear at about the appropriate point in the output, not bunched together
>near the beginning or end. Here is another attempt. This time, do the
>flushing when both are ttys or neither are.

I still don't see the point.  There is no need to do explicit flushes if
both stdout and stderr are ttys.  In the case of stdout the flush should
occur every time there's a newline.  In the case of stderr, the flush
should happen after every write.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]