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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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!feeder1.cambriumusenet.nl!feed.tweaknews.nl!138.195.8.3.MISMATCH!news.ecp.fr!feeder.eternal-september.org!eternal-september.org!newsfeed.straub-nv.de!noris.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Operation can be dispatching in only one type Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH 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> Date: Thu, 19 Nov 2009 09:50:29 +0100 Message-ID: <1iipp3bn16fe2.yqa1gz1ru17a$.dlg@40tude.net> NNTP-Posting-Date: 19 Nov 2009 09:50:29 CET NNTP-Posting-Host: a0dd1e7a.newsspool4.arcor-online.net X-Trace: DXC=F?W[8Qn0KoE[6=1B@oB@@@4IUKOGRloRYdFnSE X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:8154 Date: 2009-11-19T09:50:29+01:00 List-Id: On Wed, 18 Nov 2009 18:27:42 -0600, Randy Brukardt wrote: > "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. Only theoretically. Practically, the existing handlers of "legal" exceptions get perplexed, the stack gets wound up causing a cascade of exceptions in Finalize's. > OTOH, doing something that even generates a runtime accessibility check is a > bug Isn't it an advise to use only 'Unchecked_Access? (:-)) I think it is a problem that the code containing 'Access or upcast pointer type conversions is "suspicious", a subject of careful inspection for false positives upon accessibility check: Upcast_Ptr (P) -- Unsafe P.all'Access -- Unsafe P.all'Unchecked_Access -- "Safe" > 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. The difference is that for string bound there is a way to do it safe and for 'Access there is none (and I also agree with Robert's response.) -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de