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,67cf36c3093ae4b8
X-Google-Attributes: gid103376,public
From: Stephen Leake <Stephen.Leake@gsfc.nasa.gov>
Subject: Re: Can't be a varient record?
Date: 2000/01/27
Message-ID: <uoga7l6cz.fsf@gsfc.nasa.gov>#1/1
X-Deja-AN: 578414989
References: <388CA023.2F4001DB@alphasoft-inc.com>
X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov
X-Trace: skates.gsfc.nasa.gov 948997739 13446 128.183.220.71 (27 Jan 2000
 18:28:59 GMT)
Organization: NASA Goddard Space Flight Center
NNTP-Posting-Date: 27 Jan 2000 18:28:59 GMT
Newsgroups: comp.lang.ada
Date: 2000-01-27T18:28:59+00:00
List-Id: <comp.lang.ada>

Roga Danar <work@alphasoft-inc.com> writes:

> Hi,
> 
>   I have inherited some code and came across this type and it's
> associated "doc".
> 
>   Is the reason that record cannot be may a varient record valid?

> <snip>

The "reason" given is : 
>       Note that since this record is stored in
>       non-elaborated memory, it cannot be a variant record.

The concept "non-elaborated memory" is not an Ada concept. You'll have
to find out what that means, precisely, before you can know whether it
is still valid in your current application.

-- Stephe