From: Josiah Worcester <josiahw@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Why stdout_write checks for terminal?
Date: Tue, 21 Oct 2014 09:59:58 -0500 [thread overview]
Message-ID: <CAMAJcuCsqnQ0g3ONwswRnYaZTQDgd2U_d8Hs11DAfm-JS_qi7g@mail.gmail.com> (raw)
In-Reply-To: <20141021145640.GA5781@zx-spectrum.accesssoftek.com>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
On Tue, Oct 21, 2014 at 9:56 AM, Sergey Dmitrouk <sdmitrouk@accesssoftek.com
> wrote:
> Hi,
>
> the code in src/stdio/__stdout_write.c checks whether output is going to
> a terminal and if it's not the case disables line buffering. I'm
> wondering what's the reason behind this? This causes some programs to
> produce different output depending whether stdout is terminal or not,
> not a bit deal, but I don't see much profit in disabling buffering
> either.
>
> Regards,
> Sergey
>
From the spec <
http://pubs.opengroup.org/onlinepubs/009695399/functions/stdin.html>: "the
standard input and standard output streams are fully buffered if and only
if the stream can be determined not to refer to an interactive device."
[-- Attachment #2: Type: text/html, Size: 1210 bytes --]
next prev parent reply other threads:[~2014-10-21 14:59 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 [this message]
2014-10-21 15:17 ` Rich Felker
2014-10-21 15:40 ` Sergey Dmitrouk
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=CAMAJcuCsqnQ0g3ONwswRnYaZTQDgd2U_d8Hs11DAfm-JS_qi7g@mail.gmail.com \
--to=josiahw@gmail.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).