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,2bcab3f121e1e3a7 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder.news-service.com!newsfeed.straub-nv.de!nuzba.szn.dk!news.jacob-sparre.dk!pnx.dk!jacob-sparre.dk!ada-dk.org!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Optional body for nested generic Date: Thu, 22 Sep 2011 18:03:13 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <8ad3b626-8608-4561-8d8f-bf11e7e8efc0@en1g2000vbb.googlegroups.com> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1316732595 4861 69.95.181.76 (22 Sep 2011 23:03:15 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Thu, 22 Sep 2011 23:03:15 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-RFC2646: Format=Flowed; Original Xref: g2news1.google.com comp.lang.ada:21070 Date: 2011-09-22T18:03:13-05:00 List-Id: "Robert A Duff" wrote in message news:wcc8vpg1wje.fsf@shell01.TheWorld.com... > "Randy Brukardt" writes: ... >>...Janus/Ada had given an error message in this case, and I >> had to spend a week or so figuring out how to change our binder so that >> it >> could silently (other than a warning) drop the offending unit. > > OK, that's proof of my statement [1] above. You did it right. > You should have disputed the test, because it's truly idiotic > to silently ignore things like that. (And I claim that the > Ada 83 RM didn't really require the bad behavior -- I rewrote > chapter 10 mainly to CLARIFY that fact, not to change it.) The test was disputed (not by us, I don't think), and the ARG at the time confirmed it (I'm pretty sure there is an Ada 83 AI to this effect, but I'm too lazy to look it up right now). Ada 83 compilers had no choice but to follow this behavior. So the Ada 83 RM (at least as interpreted by the ARG and/or AVO) did require this behavior. The ACVC test was confirmed as correct. I think you could make a good case that the Ada 83 ARG was nuts in this case (and several other cases as well) -- but that doesn't change the history. The reason Ada 95 has this rule, explicitly, was to overrule that previous horrible ARG decision. You could not have done that by interpretation alone. So I continue to maintain that the rule was necessary, even if the reason that was the case was more political than technical. Randy.