Graham Barr wrote:
>
> The catch syntax is less flexable, if you wanted to catch two
> different types with the same code you are forced to either
> * duplicate code
> * put it in a sub, which is away from the statement.
> * put a switch statement in the otherwise
Could catch lists of types:
try {
}
catch Exception::Thingy, Exception::Whingy
with {
--
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
