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.1 required=5.0 tests=BAYES_20,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!attcan!uunet!husc6!ukma!uflorida!novavax!hcx1!hcx9!brucej
From: brucej@hcx9.SSD.HARRIS.COM
Newsgroups: comp.lang.ada
Subject: Re: is this a bug of my Ada compiler
Message-ID: <94700006@hcx9>
Date: 14 Oct 88 17:24:00 GMT
References: <243@cui.UUCP>
Nf-ID: #R:cui.UUCP:243:hcx9:94700006:000:1051
Nf-From: hcx9.SSD.HARRIS.COM!brucej    Oct 14 13:24:00 1988
List-Id: <comp.lang.ada>


> In the following sample code, I've been very surprised not to be warned by the
> compiler that the initial value for k was out of range:
>   procedure bug is
>   type T is range 0..255;
>   k: constant T := 16#FFE1#;
>  begin
>     null;
>   end bug;

The Verdix compiler typically does not elaborate static scalar constants.
The declaration in question merely inserts the constant `k' into the
compiler's symbol table. However, subsequent uses of the constant `k'
will be constraint checked against type `T'. In this example there are
no uses of `k'.

The new (1.10) version of the validation suite contains several tests
that enforce the requirement that constraint checks be performed on 
constant declarations.  It's a good bet that this minor bug will be fixed 
when Verdix validates VADS to 1.10.

Disclaimer: I do not work for Verdix, but for a computer vendor that
is the proud owner of a VADS source license. And yes, the 1.10 suite is 
a real pain....

----------
Bruce Jones, brucej@hcx1.harris.com
Harris Computers, Fort Lauderdale, FL