From: Andreas Schwab <schwab@linux-m68k.org>
To: Zack Weinberg <zackw@panix.com>
Cc: libc-alpha@sourceware.org, joseph@codesourcery.com,
siddhesh@gotplt.org
Subject: Re: [PATCH v2] [BZ 1190] Make EOF sticky in stdio.
Date: Mon, 12 Mar 2018 22:46:00 -0000 [thread overview]
Message-ID: <87zi3c9aks.fsf@linux-m68k.org> (raw)
In-Reply-To: <20180222002306.5998-1-zackw@panix.com> (Zack Weinberg's message of "Wed, 21 Feb 2018 19:23:06 -0500")
On Feb 21 2018, Zack Weinberg <zackw@panix.com> wrote:
> [BZ 1190]
> * libio/fileops.c (_IO_new_file_underflow): Return EOF immediately
> if the _IO_EOF_SEEN bit is already set; update commentary.
> * libio/oldfileops.c (_IO_old_file_underflow): Likewise.
> * libio/wfileops.c (_IO_wfile_underflow): Likewise.
>
> * support/support_openpty.c, support/tty.h: New files.
> * support/Makefile (libsupport-routines): Add support_openpty.
>
> * libio/tst-fgetc-after-eof.c, wcsmbs/test-fgetwc-after-eof.c:
> New test cases.
> * libio/Makefile (tests): Add tst-fgetc-after-eof.
> * wcsmbs/Makefile (tests): Add tst-fgetwc-after-eof.
Ok.
> diff --git a/libio/Makefile b/libio/Makefile
> index 3e08ed0eeb..a2e1c09e1c 100644
> --- a/libio/Makefile
> +++ b/libio/Makefile
> @@ -64,7 +64,8 @@ tests = tst_swprintf tst_wprintf tst_swscanf tst_wscanf tst_getwc tst_putwc \
> bug-memstream1 bug-wmemstream1 \
> tst-setvbuf1 tst-popen1 tst-fgetwc bug-wsetpos tst-fseek \
> tst-fwrite-error tst-ftell-partial-wide tst-ftell-active-handler \
> - tst-ftell-append tst-fputws tst-bz22415
> + tst-ftell-append tst-fputws tst-bz22415 tst-fgetc-after-eof \
Spurious backslash.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2018-03-12 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 1:04 Zack Weinberg
2018-03-12 15:31 ` Zack Weinberg
2018-03-12 22:46 ` Andreas Schwab [this message]
2018-03-13 9:52 ` Florian Weimer
2018-03-13 9:54 ` Andreas Schwab
2018-03-13 12:37 ` Zack Weinberg
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=87zi3c9aks.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
--cc=zackw@panix.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.
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).