From: Joe Buck <jbuck@synopsys.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com
Subject: Re: A new patch for libstdc++
Date: Sat, 11 Oct 1997 12:29:00 -0000 [thread overview]
Message-ID: <199710111929.MAA25299@atrus.synopsys.com> (raw)
In-Reply-To: <m0xJkZy-0004edC@ocean.lucon.org>
> It turned out the OUTOFRANGE bug is triggered by a typo. But you
> still cannot throw out_of_range in string. Here is a new patch.
I still haven't seen any test case that backs up this assertion.
Yes, recursion may result (the constructor that is throwing will
call the identical constructor), but as best I can tell, the second
call can never throw, therefore there is no problem. If you believe
otherwise, please post a case that causes an infinite recursion.
prev parent reply other threads:[~1997-10-11 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-10 17:21 H.J. Lu
1997-10-10 22:46 ` Alexandre Oliva
1997-10-11 12:29 ` Joe Buck [this message]
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=199710111929.MAA25299@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).