This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] C++ vs forced unwinding
On Tue, Apr 01, 2003 at 06:43:13PM -0500, Jason Merrill wrote:
> Hmm. It might be reasonable to make the same judgement about a throw(int)
> function, but I'm inclined to keep throw() as a special case.
Anyone else have an opinion here?
My thought is that it's surprising. There'll be code that does i/o,
catches all the exceptions caused by that, and so declares itself
throw(). Which is perfectly correct until you use it in a threaded
context.
In any case we have to make a decision soon.
r~