Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!tudelft.nl!txtfeed1.tudelft.nl!multikabel.net!newsfeed20.multikabel.net!border3.nntp.ams.giganews.com!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.saix.net!news.saix.net.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 10 Dec 2011 11:47:27 -0600
Newsgroups: comp.lang.java.programmer
Subject: Re: toward null-safe cookie cutter Comparators
References: <hkuvb758inpkqmju7aeeln2nab28i0aue6@4ax.com> <alpine.DEB.2.00.1111131750140.19917@urchin.earth.li> <onl2c7hnvjaogv8ulhti0ius9hei4ce3mp@4ax.com> <kudwq.20012$am1.18958@newsfe05.iad> <ja0t5t$kms$1@speranza.aioe.org> <icWwq.30836$Uw7.17222@newsfe02.iad> <MPG.293310ff31482c2c9896d2@202.177.16.121> <22790268.15.1321806216236.JavaMail.geo-discussion-forums@prgt40> <9e8b681f-055f-4588-9ef6-3702322b4d3e@c4g2000vbh.googlegroups.com> <2113828.215.1321914010550.JavaMail.geo-discussion-forums@prlm15> <MPG.294d5cdf98fe754a9896d3@202.177.16.121>
From: ilAn <idonot@wantspam.net>
Date: Sat, 10 Dec 2011 19:47:25 +0200
Message-ID: <m2sjkspbde.fsf@wantspam.net>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (darwin)
Cancel-Lock: sha1:RoyUJ55AuyTTJxjroIL6Qnt+AfY=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Forwarded: by - (DeleGate/9.9.1)
Lines: 24
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-bB1C0kEiLWEOu/oVsVMQViexHWtTVllVANbcr09GllKJ68+I2N3xKvEaEVBz1uvFBInNC8X6cq7PUQA!aNiGmq5GfauBfy/EmKsAixpz+pD37/P5is5COo6CEWoizTpfDn1S086fSgw=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2148
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10648

Wanja Gayk <brixomatic@yahoo.com> writes:

<snip>

>
>> > > The point is that you catch such exceptions as early as possible.
>> > 
>> > Wrong! Absolute rubbish, sorry. You catch exceptions where best
>> > handled and that may well be further up the call stack. It always
>> > depends on the situation, there is no such golden hammer for exception
>> > handling like "as early as possible".

umm.. well actually there is clear recommendation to "fail fast"...

Here is an essay from Martin Fowler's web site explaining quite
eloquently why...

http://martinfowler.com/ieeeSoftware/failFast.pdf

<snip>

>  
> Kind regards,
> Wanja