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.
Thanks for the example code. It also shows how elegantly the case statement can be used in a language that permits full-fledged expressions, rather than simple constants, in the definitions of the individual cases. Icon is so cool ... On Sat, 30 Apr 2005 11:15:04 -0700, Steve Wampler wrote: > > Steve Wampler wrote: > > ... > > For a while, I thought about trying to implement an exception handling > > mechanism using co-expressions, but just never had the heart to dive in. > > This got me thinking about it again, so I've implemented a simple > Exception handling mechanism for Unicon. (It's missing the ability > to produce a stack trace because I don't have my Unicon book at home > and couldn't figure out how to do so without it! Suggested fixes > are *welcome*.) I think this is a pretty interesting use of > co-expressions. ------------------------------------------------------- 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
