public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/4545 basic_ostream op<< should set badbit, not failbit Date: Sun, 14 Oct 2001 12:36:00 -0000 [thread overview] Message-ID: <20011014193602.25867.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/4545; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: gcc-patches@gcc.gnu.org Cc: libstdc++@gcc.gnu.org, gcc-gnats@gcc.gnu.org, brendan@zen.org, rodrigc@gcc.gnu.org Subject: Re: libstdc++/4545 basic_ostream op<< should set badbit, not failbit Date: Sun, 14 Oct 2001 15:29:12 -0400 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4545&database=gcc Hi, Following patch addresses PR 4545 on mainline. "I was mistaken in one piece that I submitted in PR libstdc++/4536. Rather, according to $27.6.2.5.3(6) the operator basic_ostream::operator<<(streambuf*) should tset badbit, not failbit, if __sbin or __xtrct is set to 0." 2001-08-02 Brendan Kehoe <brendan@zen.org> * include/bits/ostream.tcc (basic_ostream::op<<(streambuf*)): If __sbin or __xtrct are 0, set badbit, not failbit, per $27.6.2.5.3(6). *** bits/ostream.tcc.~1~ Wed Jul 18 19:19:42 2001 --- bits/ostream.tcc Thu Oct 11 14:59:02 2001 *************** namespace std *** 347,351 **** __xtrct = __copy_streambufs(*this, __sbin, __sbout); if (!__sbin || !__xtrct) ! this->setstate(ios_base::failbit); return *this; } --- 347,351 ---- __xtrct = __copy_streambufs(*this, __sbin, __sbout); if (!__sbin || !__xtrct) ! this->setstate(ios_base::badbit); return *this; } -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@mediaone.net
next reply other threads:[~2001-10-14 12:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-14 12:36 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-04 4:16 libstdc++/4545: " bkoz 2001-11-04 3:49 bkoz 2001-10-25 21:36 bkoz 2001-10-11 8:26 brendan
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=20011014193602.25867.qmail@sourceware.cygnus.com \ --to=rodrigc@mediaone.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).