public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jerry Quinn <jlquinn@optonline.net>
To: jlquinn@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10093: Regression: Setting failbit in exceptions doesn't work
Date: Sun, 23 Mar 2003 06:56:00 -0000	[thread overview]
Message-ID: <20030323065600.4628.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/10093; it has been noted by GNATS.

From: Jerry Quinn <jlquinn@optonline.net>
To: gcc-gnats@gcc.gnu.org, peturr02@ru.is, gcc-bugs@gcc.gnu.org,
 gcc-prs@gcc.gnu.org, libstdc++@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/10093: Regression: Setting failbit in exceptions doesn't
 work
Date: Sun, 23 Mar 2003 01:50:11 -0500

 I'm a bit confused by this bug.  What should the behavior be here?  To my
 simple reading of the standard, it seems that the code is operating correctly.
 
 The test case is designed to throw if failbit is set.  Failbit does get set,
 which causes the exception to be thrown.  However, it is caught in the
 exception handler and not rethrown.
 
 27.6.1.2.1 says that the exception is rethrown if badbit is set in the
 exception mask (and badbit is set), otherwise not.  This makes it sound like
 the _only_ way to get an exception from the formatted input functions is to
 set badbit in the exception mask.
 
 Petur, can you explain what I'm missing?
 
 Thanks
 Jerry Quinn


             reply	other threads:[~2003-03-23  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23  6:56 Jerry Quinn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26  2:56 Martin Sebor
2003-03-24 18:26 Pétur Runólfsson
2003-03-24 11:09 Pétur Runólfsson
2003-03-23 20:30 Martin Sebor
2003-03-23 19:26 Pétur Runólfsson
2003-03-22 15:22 paolo
2003-03-15 10:36 peturr02

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=20030323065600.4628.qmail@sources.redhat.com \
    --to=jlquinn@optonline.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jlquinn@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).