Use of exceptions is not usually something people rave about either way. Error handling is like doing dishes -- necessary, but hardly glamorous. Right now, people marvel at collections API, clever use of generics, annotations, whatever. But exceptions? People only complain about them, when they're inconveniently designed or just say nothing. I'm reluctant to say that any framework with checked exceptions in it, where people don't say anything about its exception API is a silent form of praise, but that's as good an answer as I can come up with off the cuff.
Alexey ________________________________ From: Josh Berry <[email protected]> To: [email protected] Sent: Thu, March 24, 2011 1:51:42 PM Subject: Re: [The Java Posse] How to deal with CheckedExceptions On Thu, Mar 24, 2011 at 1:43 PM, Alexey Zinger <[email protected]> wrote: > Similar principles can be devised for other kinds of API. The problem with > checked exceptions in Java is not that their very presence, but their > application in standard libraries. I wasn't limiting the search scope to the java standard lib. Is there an API that is generally regarded as having "great usage of checked exceptions?" -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
