🚀 go-pugleaf

In article <9533100.19015@mulga.cs.mu.OZ.AU> fjh@munta.cs.mu.OZ.AU (Fergus Henderson) writes:
>`throw;' would be ok in an unexpected handler only if the exception didn't
>escape, e.g.
>
>	void my_unexpected_handler() { try { throw; } catch(...) {} }
>
>and also that the example in the ARM has undefined behaviour.
>On the other hand, 15.5.2 definitely seems to assume that an
>unexpected handler can throw an exception not in the exception
>specification, and carefully describes the behaviour in that case.
>
>So the draft is self-contradictory here.  I think all you can really
>say is that one of 15.5.2 and 18.6.1.2 is wrong.

This was determined at the Valley Forge (I think) meeting. 

18.6.1.2 is simply incomplete, in that it should say that throwing a 
"bad_exception" is only allowed if "bad_exception" is in the exception
specification.

Since this was the result of an explicit vote, this should be considered
an editorial change and directed to the library working group for
handling.

-Mike Ball-
SunSoft Developer Products

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]