From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,7d3cb5920e882220 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news.glorb.com!newsfeed2.telusplanet.net!newsfeed.telus.net!edtnps89.POSTED!53ab2750!not-for-mail Newsgroups: comp.lang.ada Subject: Re: Exceptions References: <5947aa62-2547-4fbb-bc46-1111b4a0dcc9@x69g2000hsx.googlegroups.com> <475c688f$0$17524$9b4e6d93@newsspool4.arcor-online.net> <4dae26fe-0c8a-46e1-9a33-43c18cf757ae@i3g2000hsf.googlegroups.com> <9f16235c-260a-460b-873c-2183c154cc0c@e25g2000prg.googlegroups.com> From: Ray Blaak Message-ID: Organization: The Transcend User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (windows-nt) Cancel-Lock: sha1:4TQucWdZB3WhpDsy5Z9S1KEg37Y= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Dec 2007 05:29:48 GMT NNTP-Posting-Host: 154.20.94.243 X-Trace: edtnps89 1197696588 154.20.94.243 (Fri, 14 Dec 2007 22:29:48 MST) NNTP-Posting-Date: Fri, 14 Dec 2007 22:29:48 MST Xref: g2news1.google.com comp.lang.ada:18951 Date: 2007-12-15T05:29:48+00:00 List-Id: Robert A Duff writes: > Ray Blaak 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 ... ;-) 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