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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4bce46ddadaa9806 X-Google-Attributes: gid103376,public From: Robert A Duff Subject: Re: What is wrong here? (Generic and controlled types) Date: 2000/04/06 Message-ID: #1/1 X-Deja-AN: 607621456 Sender: bobduff@world.std.com (Robert A Duff) References: <38E871E6.8D9EBE71@lufmech.rwth-aachen.de> <8caebe$6us$1@nnrp1.deja.com> <8cahmn$apq$1@nnrp1.deja.com> <38EC6B3E.9225F1D4@mail.com> <8cia8a$v1j$1@nnrp1.deja.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 2000-04-06T00:00:00+00:00 List-Id: Robert Dewar writes: > It is interesting to argue about whether an RM reference would > help. The RM reference would indeed be to the section in the > RM talking about rules for deriving tagged types in terms of > accessibility levels. If you were to put in RM references, surely you would refer to all the relevant paragraphs: the rule about deriving tagged types, the definition of "library level", and the line of code in package Finalization that says Controlled is tagged. Still, I agree that this error message (and probably most error messages) shouldn't bother with RM references (at least not by default). I've seen some pretty useless ones. Eg overload resolution fails to find a unique interpretation, so it sends you into the bowels of chapter 8. - Bob