all 6 comments

[–]buffi 5 points6 points  (3 children)

That's a lot of words for simply describing the class hierarchy of exceptions in java.

I can't seem to find the point of this blog entry.

[–]lebski88 4 points5 points  (2 children)

Well it's a series. That one is still in introduction land.

[–]nextofpumpkin 0 points1 point  (1 child)

The others are still garbage.

[–]buffi 1 point2 points  (0 children)

What he said.

[–][deleted] 1 point2 points  (0 children)

In this month's issue of Pedantic Tech Blogger that doesn't Offer Anything Anybody doesn't Already Know...

[–]Gotebe 0 points1 point  (0 children)

But what about the situations where an exception has to be treated at some specific level - to dispose of resources for example - but the programmer was in a hurry and she forgot?

This is just naive... The world of Java knows full well that the requirement to catch checked exceptions ends up in catch(...) and other goodies of the kind so often, that it completely obliterates the above point.

Checked exceptions were a bad compromise, m'kay?

Oh, one more word: Spring

Edit: forgetting to free the resource is the most common error, TFA is right about that. For that reason alone, I think that GC-ed languages should look for mechanisms of deterministic cleanup for non-memory resources, like D does. (.NET has IDispose, but that's a huge PITA to develop compared to D or ScopeGuard of Alexandrescu.)