>>>>> "TO" == Tony Olekshy <[EMAIL PROTECTED]> writes: TO> Using exceptions for failure signalling is a more robust software TO> engineering technique, but only if your exception handling mechanism TO> doesn't "encourage" you to drop exceptions of the floor. Is this proven or just an assertion on your part? One issue that haven't seen addressed, is how to _not_ have exceptions. I want to use a core module (non-core can do anything they want) but I'd like to write it in procedural mode. try { $obj->method... } catch { } finally {} or $status = $obj->method... And have both work properly. <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- RFC 63 (v2) Exception handling syntax Perl6 RFC Librarian
- Re: Exceptions and Objects Piers Cawley
- Re: Exceptions and Objects Graham Barr
- Re: Exceptions and Objects Piers Cawley
- Re: Exceptions and Objects Jonathan Scott Duff
- Re: Exceptions and Objects Tony Olekshy
- Re: Dual nature (was Re: Exceptions and O... Chaim Frenkel
- Re: Dual nature (was Re: Exceptions a... Peter Scott
- Re: Dual nature (was Re: Excepti... Jonathan Scott Duff
- Re: Dual nature (was Re: Excepti... Chaim Frenkel
- Re: Dual nature (was Re: Exc... Peter Scott
- Re: Dual nature (was Re:... Chaim Frenkel
- Re: Dual nature (was Re:... 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 Peter Scott