Re: Discriminant as default initial value

[Kees de Lezenne Coulande <lezenne@COMPUSERVE.COM>]

Scott Renfro <srenfro@SIRINET.NET> 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
=====================================================================