tag:blogger.com,1999:blog-5321472228511037817.post7353755144237247852..comments2015-01-05T03:48:51.194-08:00Comments on My (Tech) User Stories: Checked exception : why the debat is not over for everyoneStephanehttp://www.blogger.com/profile/14321270550425216125noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5321472228511037817.post-10630811315889272592010-06-17T12:54:55.334-07:002010-06-17T12:54:55.334-07:00I don't know the CLU language, but what you de...I don't know the CLU language, but what you describe seems very close to RuntimeException to me, that's to say, you may either catch it or ignore it and let it bubble up (and catch it at any upper level).Stephanehttps://www.blogger.com/profile/14321270550425216125noreply@blogger.comtag:blogger.com,1999:blog-5321472228511037817.post-47044334092943357682010-06-17T08:20:24.401-07:002010-06-17T08:20:24.401-07:00The CLU language had a good solution to the proble...The CLU language had a good solution to the problem that an exception may be recoverable in some situations but not others. If an exception was not handled in the immediate calling context, it was converted to an UnhandledException exception, when then propagated up the stack until a handler was found. That solved the problem of accidentally recovering from an exception that was generated many levels down and not handled.Unknownhttps://www.blogger.com/profile/07294230278797002296noreply@blogger.comtag:blogger.com,1999:blog-5321472228511037817.post-21487953337441366262010-04-29T12:12:38.408-07:002010-04-29T12:12:38.408-07:00Great points and example.Great points and example.Sony Mathewhttps://www.blogger.com/profile/00345410246622289203noreply@blogger.com