[EMAIL PROTECTED] wrote:
One think I've always liked about Icon/Unicon is that exception handling
rarely seems necessary - most exceptions are simply handled by failure of
the containing expressions, and via the &error keyword even runtime errors
can be handled this way.
I know, that's one of the reasons I didn't dive in to this the first
time around.
One thing that exceptions give that's not so easy with
the GDE semantics is the ability to quickly exit the deeply nested code
one sees when working more with objects - instead of having to wind
one's way back through a series of propagated failures you can just
throw yourself all the way out in one operation. (The example doesn't
show this because, well, it's an example.) Of course, that isn't
as common in Icon/Unicon as with other, uh, unnamed languages, as
you note.
The other thing it provides that GDE can't (interestingly enough) is
that you can provide a reason for the 'failure' back to an enclosing
environment - and so take directed corrective action.
--
Steve Wampler [EMAIL PROTECTED]
The gods that smiled upon your birth are laughing now. -- fortune cookie
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
