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,51ab506286e54a43
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: Subtypes do not Statically Match
Date: 1999/07/01
Message-ID: <wcciu84fsjw.fsf@world.std.com>#1/1
X-Deja-AN: 495998633
Sender: bobduff@world.std.com (Robert A Duff)
References: <377A8C1A.6EFE0FF7@boeing.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-07-01T00:00:00+00:00
List-Id: <comp.lang.ada>

John Harbaugh <john.s.harbaugh2@boeing.com> writes:

> Suppose I have a record with an unconstrained array component which is
> constrained by the record discriminant.  Now I want to pass a record
> pointer (oops! access value) to a function which will return a pointer
> to the array component: [...and make heterogeneous lists of strings of
different lengths]

You can't do exactly that (as you've discovered).  But why not make a
heterogeneous list of the record objects, using pointers to the record?
Why do you want to reach inside the record and make a pointer to the
string?

- Bob
-- 
Change robert to bob to get my real email address.  Sorry.