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!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Gnat Problem - Freezing too soon Date: Sun, 03 Mar 2019 21:26:19 +0000 Organization: A noiseless patient Spider Message-ID: References: <2c369d78-70ea-4593-af3d-e014b0c1fc00@googlegroups.com> <4081906e-91de-43fa-a816-067f707c6d7d@googlegroups.com> <161c749f-b9db-465f-8ffe-7900d3a4bff5@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="57cdd2afa13e8791001b746398d5b21e"; logging-data="22124"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/RNHjp+8Z9M6KG+HETA6kud21ak9dDVUU=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (darwin) Cancel-Lock: sha1:AHIK+mAu8hl5ecMjID+DQsoR2kc= sha1:ES82nAmRFMaeW+MZTJn/OO+QiKw= Xref: reader01.eternal-september.org comp.lang.ada:55774 Date: 2019-03-03T21:26:19+00:00 List-Id: russ lyttle writes: > On 3/2/19 4:35 PM, Simon Wright wrote: >> With regard to >> >> protected type Sporadic_Agent (S: Any_Sporadic_State) >> with Priority => S.Ceiling_Prioriy >> is >> >> all the compilers are seriously confused: >> >> sporadics.ada:30:22: no selector "Ceiling_Prioriy" for type "Sporadic_State'Class" defined at line 17 >> sporadics.ada:30:23: possible misspelling of "Ceiling_Priority" >> sporadics.ada:30:23: possible misspelling of "Ceiling_Priority" >> sporadics.ada:30:23: possible misspelling of "Ceiling_Priority" >> >> and you only have to look at the task equivalent above to see that it >> should have been OK. This one looks like another compiler error to me. >> > There is a misspelling: Prioriy => Priority. Correct that misspelling > and the idiom _sometimes_ works without the "not null". Oh dear. Colour _me_ confused. > The bug report had an instance of where the compiler failed. Would it > be helpful to add an instance where it passed? Maybe so, I read once that the experts 'merely' fire up the compiler under the debugger and go straight to the source of the problem. Scary. That said, I don't see that it could hurt.