> I agree with you, this flame war is losing sense, also the original poster > dissapeared years ago.
Still here. Since I posted and discovered that my checked exceptions were masking the real issue, I've mostly removed them. Why? - Most of my checked exceptions were repackaged SQLExceptions, which are unchecked. And it's fine to be unchecked, because if I get a SQL error, I cannot do anything about it other than roll back my transaction and stop the app. - Another set of my checked exceptions were repackaged JSONExceptions. Since all my JSON is created and consumed by me, if there is a JSONException, it's a hard error and no use dealing with it. It's not like I am dealing with RESTful web services providing me with invalid JSON. - Then I had some IOException I repackged. I am still doing this as there is a remote possibility that an IOException is something the end user can fix, like if they unmount their SD card. So basically, 95% of my checked excpetion handling was for stuff the end user (or I) cannot recover from anyhow. My code is now hugely simplified and not littered with try/catch/finally blocks. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
