Re: Exceptions

[Ray Blaak <rAYblaaK@STRIPCAPStelus.net>]

Robert A Duff <bobduff@shell01.TheWorld.com> writes:
> Ray Blaak <rAYblaaK@STRIPCAPStelus.net> writes:
>> So, when the compiler demands an exception handler, then by golly they
>> provide one -- one that simply swallows the exception with a log of
>> the stack trace.
>
> This is what I don't get.  I know there are lots of not-so-good
> programmers around, but how hard could it be to teach that "junior"
> programmer how to do this particular thing right?  It's not "rocket
> science".  ;-)  And if the programmer can't learn this much, maybe
> they don't have much aptitude for programming in the first place.

The problem is that you are being logical :-).

For some unexplained reason, this bad practice simply keeps on happening. The
only thing I can think of is that the base human instinct is to go "what is
the fastest, cheapest way to shut the compiler up?".

So, one catches the exception, of course. Now what to do with it? You have to
note something useful, after all. Ah! Stack trace! To the log! Done!

Forgot to rethrow...whoops...

> ... and the senior programmer reviews the code, and gives the junior one
> a few tips, and pretty soon ... <oh, never mind> ;-)

In the end there is too much energy expended by the senior programmer
refighting the same arguments over and over.

Eventually a language is chosen where these battles simply become irrelevant.

-- 
Cheers,                                                                 Bork Bork
Ray Blaak
rblaaSTRIPCAPS@telus.net