public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Pétur Runólfsson" <peturr02@ru.is>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: libstdc++/10132: filebuf destructor throws exceptions
Date: Thu, 24 Apr 2003 18:56:00 -0000	[thread overview]
Message-ID: <20030424185600.19432.qmail@sources.redhat.com> (raw)

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

From: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= <peturr02@ru.is>
To: "Benjamin Kosnik" <bkoz@redhat.com>
Cc: <gcc-bugs@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Subject: RE: libstdc++/10132: filebuf destructor throws exceptions
Date: Thu, 24 Apr 2003 18:48:06 -0000

 > Here's something to think about. I think this is pretty good.=20
 > Something like it will have to be done for the corresponding=20
 > underflow bits.
 
 Maybe I'm missing something, but how does this fix the bug if
 some exceptions are rethrown?
 
 Also, what's the rationale behind rethrowing some but not all
 exceptions?
 
 I don't think that basic_filebuf should catch exceptions thrown
 by use_facet or codecvt members. It is clear from 27.6.2.1 etc.
 that streambuf members may throw; if underflow() fails because
 an exception is thrown badbit, not eofbit, should be set in
 rdstate(); and if badbit is set in exceptions() the original
 exception should be rethrown.
 
 Petur
 


             reply	other threads:[~2003-04-24 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 18:56 Pétur Runólfsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-28 16:00 bkoz
2003-04-25 21:56 Pétur Runólfsson
2003-04-25 21:46 Pétur Runólfsson
2003-04-25  0:56 Benjamin Kosnik
2003-04-24 22:26 Benjamin Kosnik
2003-04-24 22:06 Benjamin Kosnik
2003-04-24  6:06 Benjamin Kosnik
2003-04-24  6:06 Benjamin Kosnik
2003-04-23  8:56 Pétur Runólfsson
2003-04-23  3:47 bkoz
2003-04-22  1:08 bkoz
2003-03-18 12:16 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=20030424185600.19432.qmail@sources.redhat.com \
    --to=peturr02@ru.is \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@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).