Comments on: Bad Programming: How not to use try/catch blocks http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/ Thoughts on life, liberty, and information technology Tue, 24 Jan 2012 10:43:34 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: brian http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-240898 brian Wed, 02 Jul 2008 13:43:02 +0000 http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-240898 Having a try/catch block without anything in the catch is like fishing and never looking at what's on the hook. Having a try/catch block without anything in the catch is like fishing and never looking at what’s on the hook.

]]> By: harborpirate http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-236209 harborpirate Fri, 27 Jun 2008 21:10:50 +0000 http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-236209 Even worse is that in many cases you take a performance hit (though slight) for adding an exception handling routine. This is a great trade-off when you get a more robust application out of it since the difference is extremely small. When you have an empty catch you're screwing yourself twice. Errors won't bubble out to the calling software so you won't know what happened AND your code will run ever so slightly slower. Even worse is that in many cases you take a performance hit (though slight) for adding an exception handling routine. This is a great trade-off when you get a more robust application out of it since the difference is extremely small. When you have an empty catch you’re screwing yourself twice. Errors won’t bubble out to the calling software so you won’t know what happened AND your code will run ever so slightly slower.

]]> By: brian http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-222280 brian Thu, 12 Jun 2008 19:26:29 +0000 http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-222280 VB... the language that should not be. VB… the language that should not be.

]]> By: Lucas http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-222266 Lucas Thu, 12 Jun 2008 18:47:14 +0000 http://www.sidesofmarch.com/index.php/archive/2008/06/12/bad-programming-how-not-to-use-trycatch-blocks/#comment-222266 Sounds familiar! I recently went through the source code of a production application adding (at least) some logging code into hundreds (well, maybe just dozens) of empty catches. It was VERY frustrating when the client reported a problem and sent us log files, and the logs didn't have the slightest hint of what the problem was. Here we say the application "eats" the exceptions. om nom nom nom ... The fact that it was written in VB was also frustrating, but that's just me :) Sounds familiar! I recently went through the source code of a production application adding (at least) some logging code into hundreds (well, maybe just dozens) of empty catches.

It was VERY frustrating when the client reported a problem and sent us log files, and the logs didn’t have the slightest hint of what the problem was. Here we say the application “eats” the exceptions. om nom nom nom …

The fact that it was written in VB was also frustrating, but that’s just me :)

]]>