public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/96161] New: istream::ignore sets eofbit too soon Date: Fri, 10 Jul 2020 21:10:45 +0000 [thread overview] Message-ID: <bug-96161-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96161 Bug ID: 96161 Summary: istream::ignore sets eofbit too soon Product: gcc Version: 10.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- #include <sstream> #include <iostream> int main() { std::istringstream s("++"); s.ignore(2, '-'); std::cout << "EOF? " << s.eof() << std::endl; } This shows that we set eofbit when the end of the stream is reached, even though we have already discarded as many characters as requested. Libc++ and MSVC do not set eofbit here.
next reply other threads:[~2020-07-10 21:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-10 21:10 redi at gcc dot gnu.org [this message] 2020-07-10 22:55 ` [Bug libstdc++/96161] " redi at gcc dot gnu.org 2020-07-13 11:26 ` cvs-commit at gcc dot gnu.org 2020-07-13 11:33 ` redi at gcc dot gnu.org 2020-08-06 19:47 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org
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=bug-96161-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).