Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Grokking exceptions 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • FWIW, I've noticed more discussion of whether checked exceptions in Java are worth the effort, particularly since they're not implemented in C#. There's a good writeup [mindview.net] on the issues from Bruce Eckel, along with some related discussion [mindview.net].

    • Absolutely wonderful writeup! That definitely makes the think that checked exceptions might not be the WunderTool that I thought. The problem appears to lie in programmers being pressed for time and thus "swallowing" exceptions with the intent to come back to them later. We all know what a lie "I'll do it tomorrow" is :)

      try {
        doSomethingWith(foo);
      } catch (SomeException e) {} /* exception swallowed */

      Knowing full well that I'm often under the gun at work, I could easily see myself doing that with every intent of coming back to it. Three thousand lines of code later ...

      There is one benefit to checked exceptions that I see. If I am using third-party software, I might not be aware of all of the exceptions that it throws. It would be nice to see the uncaught exceptions at compile time. Shipping a product after having failed to trap the YourCPUIsOverheating exception would definitely be a damper on my day (and perhaps my paycheck). Why would I fail to trap it? It's in the docs, right? And I'm going to read the docs tomorrow. Really.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.