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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Michael B." Newsgroups: comp.lang.ada Subject: Re: Access parameters and accessibility Date: Thu, 18 Dec 2014 18:48:32 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <4f547857-ea9e-4baf-a705-911fbf9c633d@googlegroups.com> <72048e0e-164a-4dce-8818-69454011a618@googlegroups.com> NNTP-Posting-Host: BwT254shNqiZ3mfME3kSUA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:24121 Date: 2014-12-18T18:48:32+01:00 List-Id: On 12/17/14 16:41, sbelmont700@gmail.com wrote: > It sounds very much like a compiler bug; regardless of the mechanism > that the compiler writer chooses to use to implement the rules of the > language, it must in fact implement them correctly and completely > (i.e. all those conversions should pass, no matter if they use the > model proposed in the paper, or something else entirely). That makes sense. So it seems my misunderstanding came from too much trust in a compiler...