mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Sergey Dmitrouk <sdmitrouk@accesssoftek.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: Why stdout_write checks for terminal?
Date: Tue, 21 Oct 2014 18:40:35 +0300	[thread overview]
Message-ID: <20141021154035.GA5902@zx-spectrum.accesssoftek.com> (raw)
In-Reply-To: <20141021151727.GD22465@brightrain.aerifal.cx>

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


      reply	other threads:[~2014-10-21 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 14:56 Sergey Dmitrouk
2014-10-21 14:59 ` Josiah Worcester
2014-10-21 15:17 ` Rich Felker
2014-10-21 15:40   ` Sergey Dmitrouk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141021154035.GA5902@zx-spectrum.accesssoftek.com \
    --to=sdmitrouk@accesssoftek.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).