I actually liked their arguments too and concur with your finding on Spring. I've always been an upwind sailor. I got really into Pascal's strong typing when everybody else was eschewing it for C, then moved into Lisp and Smalltalk when everybody else was into C++ and now Java.
Jeff Jeff Eastman, Ph.D. Windward Solutions Inc. +1.415.298.0023 http://windwardsolutions.com http://jeffeastman.blogspot.com > -----Original Message----- > From: Ted Dunning [mailto:[EMAIL PROTECTED] > Sent: Monday, March 31, 2008 9:02 AM > To: mahout-dev@lucene.apache.org > Subject: Re: [jira] Updated: (MAHOUT-22) Several matrix exceptions are > checked exceptions, but should be unchecked > > > My history is that I was once strongly in the "declare it" camp. > > The example of Spring's JDBC support completely won me over to the other > side. The arguments didn't convince me, but using their code did. If you > don't expect the programmer to be able to do anything, and you expect them > to live in a framework (like the servlet or map/reduce) that doesn't > declare > these exceptions, then you are just making code really complex when it > doesn't need to be. > > > On 3/31/08 8:50 AM, "Jeff Eastman" <[EMAIL PROTECTED]> wrote: > > > I think there is some value in requiring users to handle them > explicitly, > > but can see both arguments. I do not feel strongly about this one.
