From: Paul Eggert <eggert@cs.ucla.edu>
To: Frank da Cruz <fdc@columbia.edu>
Cc: Liam Stitt <stittl@cuug.ab.ca>, Mike <michael@rmrco.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: C-kermit fails
Date: Sat, 1 Aug 2020 01:07:53 -0700 [thread overview]
Message-ID: <a931305f-921a-7224-6f75-2b576c0fcef8@cs.ucla.edu> (raw)
In-Reply-To: <CAKqtx98=KJ_5Be74qnjrKQmSSwOGQog5S1sN66ZZFs=MCELcFw@mail.gmail.com>
On 7/31/20 5:17 PM, Frank da Cruz wrote:
> what harm is there in leaving the stdin buffering items where they have
> been all these years?
I don't know and I'm too lazy to look up whether it was for thread-safety or
buffer safety or performance or whatever. I seriously doubt whether some glibc
developer said, "Oh, let's change stdio internals for no good reason."
prev parent reply other threads:[~2020-08-01 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 16:29 C-kermit fails Mike
2020-07-24 16:33 ` Florian Weimer
2020-07-24 17:36 ` Zack Weinberg
2020-07-24 18:47 ` Paul Eggert
2020-07-24 19:41 ` Frank da Cruz
2020-07-24 19:45 ` Frank da Cruz
2020-07-24 20:05 ` Zack Weinberg
2020-07-27 8:10 ` Florian Weimer via Libc-alpha
2020-07-24 21:07 ` Paul Eggert
2020-07-24 23:45 ` Frank da Cruz
2020-07-25 1:59 ` Paul Eggert
2020-07-31 12:41 ` Maciej W. Rozycki
2020-07-31 18:22 ` Frank da Cruz
2020-07-31 20:23 ` Paul Eggert
2020-08-01 0:17 ` Frank da Cruz
2020-08-01 8:07 ` Paul Eggert [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a931305f-921a-7224-6f75-2b576c0fcef8@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=fdc@columbia.edu \
--cc=libc-alpha@sourceware.org \
--cc=michael@rmrco.com \
--cc=stittl@cuug.ab.ca \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).