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,FREEMAIL_FROM, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,da74d35864a7d542 X-Google-Attributes: gid103376,public From: Kees de Lezenne Coulande Subject: Re: Discriminant as default initial value Date: 1997/03/30 Message-ID: <199703301300_MC2-1377-42B7@compuserve.com>#1/1 X-Deja-AN: 229477763 Sender: Ada programming language Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Newsgroups: comp.lang.ada Date: 1997-03-30T00:00:00+00:00 List-Id: Scott Renfro wrote: >I want to use a discriminant in a record as both a bound in the index >constraint of a component declaration and as a default initial value. >I'm not sure that this is allowed by the RM. > >The following example, while contrived, exhibits behavior that I >definitely do not understand. Using GNAT 3.09 for NT with Max defined >before the Position Matrix, the component record is initialized as >expected. When Max is defined after the Position Matrix within the >record, Max is initialized to a large value that is not even within the >subtype's range. No exception is raised. > >Is this expected behavior? Is it permissible to use the same >discriminant as both an index bound and a default initial value? Should >the behavior change when the order of declaration within the record >changes? Scott, I tried both versions of your example using GNAT 3.09 for OS/2, and found no problems. Maybe it is just the Windows version of GNAT playing up again. Kees de Lezenne Coulander --------------------------------------------------------------------- C.M. de Lezenne Coulander Amsterdam-Zuidoost The Netherlands E-mail: lezenne@compuserve.com Aircraft Development and Systems Engineering B.V. Schiphol-Rijk, The Netherlands =====================================================================