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,b6e8251cd11c860d
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Renaming record discriminants.
Date: 1996/04/02
Message-ID: <dewar.828448853@schonberg>#1/1
X-Deja-AN: 145421262
references: <Dp75Aq.B1o@ssd.ray.com> <Dp7Eoo.FLK.0.-s@inmet.camb.inmet.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-04-02T00:00:00+00:00
List-Id: <comp.lang.ada>

Tuck said:

":    type Record_Type(Has_Value : Boolean) is
:        record
:          case Has_Value is
:             when True =>
:               Value : Integer;
:             when False =>
:                 null;
:          end case;

:    Object : Record_Type := (Has_Value => True, Value => 1);

:    Discriminant : Boolean renames Object.Has_Value; -- error
:    Component : Integer renames Object.Value; -- error

: (there may be a typo or something in there, this is off the top of my head)

: The Intermetrics compiler I am using complains that:
: Object.Has_Value depends on discriminants of an unconstrained formal
: parameter with default discriminants [RM_95 8.5.1(5)]

If it really complains, then this is a compiler bug.
I have not been able to reproduce this problem with
a recent version of this compiler, so you should submit
a formal bug report if you have a (ideally minimal) test
case that shows the problem."

Gee Tuck, I trust the intermetrics compiler *does* complain about
the missing "end record" in the above example :-) :-)