public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, schmid@snake.iap.physik.tu-darmstadt.de
Subject: Re: libstdc++/6750: ofstream incorrectly sets failbit (severe regression)
Date: Thu, 23 May 2002 07:55:00 -0000	[thread overview]
Message-ID: <20020523145513.1163.qmail@sources.redhat.com> (raw)

Synopsis: ofstream incorrectly sets failbit (severe regression)

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Thu May 23 07:55:12 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: analyzed->feedback
State-Changed-By: bkoz
State-Changed-When: Thu May 23 07:55:12 2002
State-Changed-Why:
    Peter, I appreciate this bug report. Have you looked at libstdc++/6518?
    
    
    #include <iostream>
    
    int main()
    {
      char* pt = NULL;
      std::cout << pt << std::endl;
      return 0;
    }
    
    This no longer cores, but it does set bad bit. You seem to think that setting badbit is not good. Well then, what? Throw an exception (which was suggested on the reflector list, but I think compatibility with streambuf* NULL is a better fit.) Do you agree that this is unspecified behavior? 
    
    -benjamin

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6750


             reply	other threads:[~2002-05-23 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23  7:55 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27  2:36 bkoz
2002-05-23 16:06 Peter Schmid
2002-05-20 14:09 paolo
2002-05-20 13:36 Peter Schmid

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=20020523145513.1163.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=schmid@snake.iap.physik.tu-darmstadt.de \
    /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).