On Thu, Aug 10, 2000 at 07:47:47PM -0600, Tony Olekshy wrote: > With the approach proposed in RFC 88 (Structured Exception > Handling Mechanism), you could write that as: > > try { > } catch { > switch ($_[0]->name) { > case IO { ... } > case Socket { ... } > } > } Nope, the error are objects, so you need to allow for inheritance. Graham.
- Re: RFC 80 (v1): Exception objects and cl... Peter Scott
- Re: RFC 80 (v1): Exception objects an... Jeremy Howard
- Re: RFC 80 (v1): Exception objects an... Graham Barr
- Re: RFC 80 (v1): Exception objec... John Porter
- Re: RFC 80 (v1): Exception o... Graham Barr
- Re: RFC 80 (v1): Exception o... John Porter
- Re: RFC 80 (v1): Exception o... Peter Scott
- Re: RFC 80 (v1): Exception o... Graham Barr
- Re: RFC 80 (v1): Exception objects and classes fo... Jonathan Scott Duff
- Re: RFC 80 (v1): Exception objects and classes for bui... Tony Olekshy
- Graham Barr