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: a07f3367d7,dbbbb21ed7f581b X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.78.MISMATCH!feeder.news-service.com!de-l.enfer-du-nord.net!gegeweb.org!news.ecp.fr!news.jacob-sparre.dk!pnx.dk!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Operation can be dispatching in only one type Date: Wed, 18 Nov 2009 18:27:42 -0600 Organization: Jacob Sparre Andersen Message-ID: References: <025105f2-5571-400e-a66f-ef1c3dc9ef32@g27g2000yqn.googlegroups.com> <94e76749-c49c-45aa-b7dc-386da0d71c66@e4g2000prn.googlegroups.com> <1u0im1tdws15u.1n9v9rz7bu4t4$.dlg@40tude.net> <39kf90ha60px$.d7746cf5cx6h.dlg@40tude.net> <691d6892-bc5e-4d81-8025-c36556bf2593@13g2000prl.googlegroups.com> <1h9hilcg5i6il.12edpgu4szw1h.dlg@40tude.net> <1wtsriaxu0s4s$.ikwnnz5teukp$.dlg@40tude.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1258590464 20620 69.95.181.76 (19 Nov 2009 00:27:44 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Thu, 19 Nov 2009 00:27:44 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Xref: g2news1.google.com comp.lang.ada:8149 Date: 2009-11-18T18:27:42-06:00 List-Id: "Dmitry A. Kazakov" wrote in message news:1wtsriaxu0s4s$.ikwnnz5teukp$.dlg@40tude.net... ... >> OK, I don't understand this. First, I don't understand what about >> accessibility checks was a disaster; > > Because they are the major contributor to hours spent on debugging > unhandled exceptions. That seems odd to me. I rather *like* getting unhandled exceptions, because it is almost always easy to see what the problem is from the exception name and the traceback. (And all of my long-running programs have systems to record this in the case of an unexpected exception.) It's the incorrect results, compiler bugs (where the code is right, but the wrong thing happens), and crashes that cause "hours of debugging". OTOH, doing something that even generates a runtime accessibility check is a bug IMHO (it's what Bob Duff calls a "tripping hazard" - a latent problem that will bite you when someone does something unconventional -- in that sense it is just like the bug of assigning a string parameter has lower bound 1); it would be useful if the compiler could optionally point out such places so you could fix them. Randy.