Comments on: Fail-Fast Pattern/Policy http://dotnetworkaholic.com/fail-fast-pattern/ Atlanta ASP.Net MVC Developer/ Architect Fri, 16 Jul 2010 05:20:24 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Jerry Dennany http://dotnetworkaholic.com/fail-fast-pattern/comment-page-1/#comment-4020 Jerry Dennany Fri, 05 Dec 2008 18:15:06 +0000 http://dotnetworkaholic.com/fail-fast-patternpolicy-fail-early-with-context/#comment-4020 You mentioned walking up the call stack to get the previous MethodInfo. I demo something like this with Tracing in an article here: <br> <br><a target="_new" href="http://www.codeproject.com/csharp/customtracelistener.asp" rel="nofollow">http://www.codeproject.com/csharp/customtracelistener.asp</a> <br> You mentioned walking up the call stack to get the previous MethodInfo. I demo something like this with Tracing in an article here:

http://www.codeproject.com/csharp/customtracelistener.asp

]]> By: Paul Lockwood http://dotnetworkaholic.com/fail-fast-pattern/comment-page-1/#comment-4019 Paul Lockwood Fri, 05 Dec 2008 18:14:50 +0000 http://dotnetworkaholic.com/fail-fast-patternpolicy-fail-early-with-context/#comment-4019 Yup throwing exceptions is expensive, I found that out the hard way. When first writing .Net code I used Exceptions to indicate 'expected errors' - i.e. broken business rules, validation errors etc which happen all the time. Not a wise idea! <br> <br>As I understand it the main point with Fail-Fast is to throw an exception when the code would fail anyway. In almost every case I use the technique it is in places that an error SHOULD never happen, when some inevitably do using fail-fast prepares the ground for spotting the root cause. <br> <br>Allowing Exceptions to bubble up the code [wry smile] That's always a good one to get developers arguing especially Java people who generally miss their checked exceptions. Yup throwing exceptions is expensive, I found that out the hard way. When first writing .Net code I used Exceptions to indicate ‘expected errors’ – i.e. broken business rules, validation errors etc which happen all the time. Not a wise idea!

As I understand it the main point with Fail-Fast is to throw an exception when the code would fail anyway. In almost every case I use the technique it is in places that an error SHOULD never happen, when some inevitably do using fail-fast prepares the ground for spotting the root cause.

Allowing Exceptions to bubble up the code [wry smile] That’s always a good one to get developers arguing especially Java people who generally miss their checked exceptions.

]]> By: Sean Schade http://dotnetworkaholic.com/fail-fast-pattern/comment-page-1/#comment-4018 Sean Schade Tue, 27 Jul 2004 23:11:58 +0000 http://dotnetworkaholic.com/fail-fast-patternpolicy-fail-early-with-context/#comment-4018 Excellent point Paul. Exceptions are expensive to throw, but hours or even days of debugging are much more expensive! I have never been a fan of just letting an exception bubble up to the calling code. Usually the context of the exception is so irrelevant at that point that it becomes useless. Excellent point Paul. Exceptions are expensive to throw, but hours or even days of debugging are much more expensive! I have never been a fan of just letting an exception bubble up to the calling code. Usually the context of the exception is so irrelevant at that point that it becomes useless.

]]>