[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141021154035.GA5902@zx-spectrum.accesssoftek.com>
Date: Tue, 21 Oct 2014 18:40:35 +0300
From: Sergey Dmitrouk <sdmitrouk@...esssoftek.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: Why stdout_write checks for terminal?
On Tue, Oct 21, 2014 at 08:17:27AM -0700, Rich Felker wrote:
> Full buffering _must_ be disabled if the underlying file is an
> "interactive device" (terminal); this is a requirement of the
> standards. Somewhere in the distant past musl always put stdout in
> line-buffered mode, but users complained (rightfully) because programs
> writing binary data to stdout (e.g. things like djpeg) were 10-100x
> slower than with other libcs, so now whether it's line or full
> buffered depends on whether it's a terminal.
Thanks for the explanation (and to Josiah as well), that makes sense.
Related commit message is missing details and it wasn't really clear
why this change is needed.
Regards,
Sergey
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
