Piers Cawley wrote: > > The (continue|always|finally|whatever) clause will *always* be > executed, even if one of the catch clauses does a die, so you can use > this to roll back the database transaction or whatever else was going > on and restore any invariants. Which makes me think that it would be nice if the continue block could come before the catch block(s): establish_invariants(); try { something_risky(); } continue { restore_invariants(); } catch { handle_error_assuming_invariants_restored(); } -- John Porter
- RFC 80 (v1): Exception objects and classes for builtin... Jonathan Scott Duff
- Re: RFC 80 (v1): Exception objects and classes fo... Peter Scott
- Re: RFC 80 (v1): Exception objects and classes fo... Graham Barr
- Re: RFC 80 (v1): Exception objects and classe... Peter Scott
- Re: RFC 80 (v1): Exception objects and cl... Graham Barr
- Re: RFC 80 (v1): Exception objects an... John Porter
- Re: RFC 80 (v1): Exception objects an... Peter Scott
- Re: RFC 80 (v1): Exception objec... Chaim Frenkel
- Re: RFC 80 (v1): Exception o... Piers Cawley
- Re: RFC 80 (v1): Excepti... John Porter
- Re: RFC 80 (v1): Excepti... Piers Cawley
- Re: RFC 80 (v1): Excepti... Chaim Frenkel
- Re: RFC 80 (v1): Excepti... Piers Cawley
- Re: RFC 80 (v1): Excepti... Chaim Frenkel
- Re: RFC 80 (v1): Excepti... John Porter
- Re: RFC 80 (v1): Excepti... Tony Olekshy
- Re: RFC 80 (v1): Exception objects an... Peter Scott
- Re: RFC 80 (v1): Exception objects and cl... Bart Lateur
- Re: RFC 80 (v1): Exception objects an... Peter Scott
- Re: RFC 80 (v1): Exception objects and classe... Chaim Frenkel