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/17 Message-ID: #1/1 X-Deja-AN: 197021938 references: <9611150709.AA09539@algol.ocag.ch> <328DE73D.581B@lmtas.lmco.com> organization: New York University newsgroups: comp.lang.ada Date: 1996-11-17T00:00:00+00:00 List-Id: 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. As for requirements, there is not even a requirement that error messages be generated for illegal programs, since again messages are entirely outside the language definition. The only semantic requirement is that the library (Ada 83) or compilation environment (Ada 95) not be affected by compiling an illegal unit.