This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Exceptions, one more time
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
I've written about this post from Joel twice now - here and here. Lots of other people (here, for instance) put up their thoughts as well. I expected a response from Joel, but I was kind of surprised at what he wrote - have a look at yesterday's post on the subject. Basically, he opts out of the issue:
There's no perfect way to write code to handle errors. Arguments about whether exception handling is "good" or "bad" quickly devolve into disjointed pros and cons which never balance each other out, the hallmark of a religious debate. There are lots of good reasons to use exceptions, and lots of good reasons not to. All design is about tradeoffs. There is no perfect design and there is certainly never any perfect code.
The above is true enough, but it's a way around the discussion, not really an entry into it. Disappointing.
Previous Topic
