Actions

icon Post
text/html Subscribe
text/html Unsubscribe
CodeSourcery > List Archives
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Explicit catch of forced unwind

  • To: Mark Mitchell <mark@xxxxxxxxxxxxxxxx>
  • Subject: Re: Explicit catch of forced unwind
  • From: Jason Merrill <jason@xxxxxxxxxx>
  • Date: Sun, 15 Apr 2007 19:31:25 -0400
Mark Mitchell wrote:

Jason Merrill wrote:



My current implementation doesn't do this, it just changes the
personality function to magically match a forced unwind with the
__forced_unwind type.


I see; that's clever.  I also see that your proposed changes to the
specification forbid users from poking at the exception object,
presumably to permit this implementation technique.


Yes.


However, the "accessed in any way" language would also seem to forbid
rethrowing the exception (via "throw;").  Did you meant to forbid that?
If so, why?
No, rethrowing does not access the exception, just passes it along. This is the same restriction that was already present for foreign exceptions. 

Jason