Actions
| Post | |
| Subscribe | |
| Unsubscribe |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [c++-pthreads] Re: Explicit catch of forced unwind
- To: Jason Merrill <jason@xxxxxxxxxx>
- Subject: Re: [c++-pthreads] Re: Explicit catch of forced unwind
- From: Mark Mitchell <mark@xxxxxxxxxxxxxxxx>
- Date: Sun, 15 Apr 2007 17:15:04 -0700
Jason Merrill wrote: >> 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. OK; in that case, your proposed change seems fine to me. Does anyone else object? If nobody speaks up in a week, I'll check the change into the ABI document. Thanks, -- Mark Mitchell CodeSourcery mark@xxxxxxxxxxxxxxxx (650) 331-3385 x713
- References:
- Re: Explicit catch of forced unwind
- From: Jason Merrill
- Re: Explicit catch of forced unwind
- From: Mark Mitchell
- Re: Explicit catch of forced unwind
- From: Jason Merrill
- Re: Explicit catch of forced unwind
- Prev by Date: Re: Explicit catch of forced unwind
- Next by Date: [c++-pthreads] question about using of malloc / free in pthreads
- Previous by thread: Re: Explicit catch of forced unwind
- Next by thread: [c++-pthreads] question about using of malloc / free in pthreads
- Index(es):