>>>>> "PC" == Piers Cawley <[EMAIL PROTECTED]> writes: PC> The (continue|always|finally|whatever) clause will *always* be PC> executed, even if one of the catch clauses does a die, so you can use PC> this to roll back the database transaction or whatever else was going PC> on and restore any invariants. Err, how does one differentiate between a 'good' entry and a 'bad' entry. PC> Note too that we don't need to do any case based magic, we can and PC> should use polymorphism for that. Why? Just because? <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- Re: RFC 80 (v1): Exception objects and classes for builtins Peter Scott
- Re: RFC 80 (v1): Exception objects and classes for builtins Graham Barr
- Re: RFC 80 (v1): Exception objects and classes for buil... Peter Scott
- Re: RFC 80 (v1): Exception objects and classes for ... Graham Barr
- Re: RFC 80 (v1): Exception objects and classes ... John Porter
- Re: RFC 80 (v1): Exception objects and classes ... Peter Scott
- Re: RFC 80 (v1): Exception objects and clas... Chaim Frenkel
- Re: RFC 80 (v1): Exception objects and... Piers Cawley
- Re: RFC 80 (v1): Exception objects... John Porter
- Re: RFC 80 (v1): Exception objects... Piers Cawley
- Re: RFC 80 (v1): Exception objects... Chaim Frenkel
- Re: RFC 80 (v1): Exception objects... Piers Cawley
- Re: RFC 80 (v1): Exception objects... Chaim Frenkel
- Re: RFC 80 (v1): Exception objects... John Porter
- Re: RFC 80 (v1): Exception objects... Tony Olekshy
- Re: RFC 80 (v1): Exception objects and classes ... Peter Scott
- Re: RFC 80 (v1): Exception objects and classes for ... Bart Lateur
- Re: RFC 80 (v1): Exception objects and classes for buil... Chaim Frenkel
- Re: RFC 80 (v1): Exception objects and classes for ... Graham Barr
- Re: RFC 80 (v1): Exception objects and classes ... Chaim Frenkel