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++/28103] std::operator<<(ostream&, string) sets badbit instead of failbit on failure
Date: Thu, 13 Jun 2024 16:13:06 +0000 [thread overview]
Message-ID: <bug-28103-4-8Ul1mdMjTY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28103-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28103
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> The requirement to set failbit came from
> https://cplusplus.github.io/LWG/issue211 and certainly seems consistent with
> other input operations, which set failbit not badbit.
>
> N.B. https://wg21.link/p1264r2 cleaned up the wording for input operations,
> making it clear that badbit should only be set by the library after an input
> operation throws an exception.
Oops that's for input ops and this is about output!
next prev parent reply other threads:[~2024-06-13 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28103-4@http.gcc.gnu.org/bugzilla/>
2024-06-13 16:09 ` redi at gcc dot gnu.org
2024-06-13 16:13 ` redi at gcc dot gnu.org [this message]
2024-06-13 16:13 ` redi at gcc dot gnu.org
2024-06-13 16:45 ` redi at gcc dot gnu.org
2024-06-13 17:17 ` redi at gcc dot gnu.org
2024-06-14 11:15 ` redi at gcc dot gnu.org
2006-06-20 18:21 [Bug libstdc++/28103] New: " sebor at roguewave dot com
2006-06-20 19:09 ` [Bug libstdc++/28103] " pcarlini at suse dot de
2006-06-22 16:28 ` pcarlini at suse dot de
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-28103-4-8Ul1mdMjTY@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: 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).