Jonathan Scott Duff <[EMAIL PROTECTED]> writes: > On Sun, Aug 13, 2000 at 07:27:47PM -0700, Peter Scott wrote: > > At 12:22 PM 8/12/00 -0500, Jonathan Scott Duff wrote: > > Pretty much. It screams O-O for these reasons: > > > > An exception is an 'error'. That's already a vague concept. > > > > An error has text associated with it, but also a bunch of other attributes. > > So it's a structured data type ... where does OOP come into play? Because once you bless it into a class by default then you can use OO based dispatch, have exceptions that know how to handle themselves and other good stuff. You are, of course, free to ignore the OO bells and whistles and just treat it as structured data and do your own handling. -- Piers
- Re: RFC 63 (v2) Exception handling syntax Peter Scott
- Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Tony Olekshy
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Tony Olekshy
- Re: Exceptions and Objects Peter Scott
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Peter Scott
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Piers Cawley
- Re: Exceptions and Objects Piers Cawley
- Re: Exceptions and Objects Tony Olekshy
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Tony Olekshy
- Re: Exceptions and Objects David L. Nicol
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Graham Barr
- Re: Exceptions and Objects Tony Olekshy
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Graham Barr
- Re: Exceptions and Objects Jonathan Scott Duff