tag:blogger.com,1999:blog-11616517.post8553353487584784825..comments2009-12-29T16:10:52.449+01:00Pierre-Antoine Grégoirehttp://www.blogger.com/profile/07978146278885763776noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11616517.post-70465932828873093322009-12-29T16:10:52.449+01:002009-12-29T16:10:52.449+01:00Hello Guru, what entice you to post an article. This article was extremely interesting, especially since I was searching for thoughts on this subject last Thursday. <br /><br />rH3uYcBXAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-11616517.post-231331923949078182007-04-24T21:01:00.000+02:002007-04-24T21:01:00.000+02:00I guess I am pretty lazy because when I have a dependency that forces me to deal with more than a couple of checked exceptions, I catch wide (java.lang.Exception), wrap and re-throw (or log and swallow).<BR/><BR/>This is unfortunate because there are situations where I want to catch wide (for example, to prevent a caller to receive any exception): it is impossible, by reading the code, to figure out if I am catching wide on purpose or because the called methods are throwing too many checked exceptions (unless I document it).<BR/><BR/>So: yeah, let's add more syntactic sugar to the Jav!David Dossothttp://www.blogger.com/profile/13987512594987806769noreply@blogger.com