Explicit catch of forced unwind

[Jason Merrill]

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