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,4576669b9167cd1d X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: NVRAM or how can I enforce a range check in Ada83. Date: 1996/11/22 Message-ID: #1/1 X-Deja-AN: 198245644 references: <9611150709.AA09539@algol.ocag.ch> <328DE73D.581B@lmtas.lmco.com> <3295FF52.1F2C@lmtas.lmco.com> organization: New York University newsgroups: comp.lang.ada Date: 1996-11-22T00:00:00+00:00 List-Id: Ken says "Robert Dewar wrote: > > Ken Garlington says > > "There is an Ada 83 interpretation that says compilers are permitted to warn > you if the Source and Target are of different sizes on an unchecked conversion , > but as I understand it this isn't a requirement." > > This is not right. No interpretation is needed to permit a compiler to > generate warning messages, a compiler can generate whatever warning > messages it likes, since these are entirely outside the language. There is an Ada 83 AI that includes these words. It may not be a well-written AI , but it does exist. My browser is behaving badly at the moment, but perhaps you could go look at the Ada 83 AI written about Unchecked_Conversions between sourc e and target of different sizes, and explain where I misunderstood the words." This might well be mentioned in an AI, but is not part of the interpretation, just a useful reminder to the reader that compilers are ALWAYS allowed to generate warnings about anything that they want. An AI might often point out that it is quite reasonable to issue a warning in some given situation, but in no sense is the AI *granting* that permissing, which always exists, regardless of any AI's.