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,2d5d6ef785dd656e,start
X-Google-Attributes: gid103376,public
From: paul williams <paul_williams@itd.sterling.com>
Subject: Apex problem w/aliased variables
Date: 1996/11/13
Message-ID: <328A5934.1EED@itd.sterling.com>#1/1
X-Deja-AN: 196603077
content-type: text/plain; charset=us-ascii
organization: Sterling Software ITD
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.0 (WinNT; I)
Date: 1996-11-13T00:00:00+00:00
List-Id: <comp.lang.ada>


We are developing a large scientific application using Ada95 
with the Rational Apex tool. Our design depends heavily on being 
able to take advantage of the new access mechanism for 
non-allocated variables. However, the Apex analyzer reports an 
error when attempting to assign the access attribute of an 
aliased variable to a pointer that is appropriately declared for 
the entire class. See code sample followed by error report 
below. Is anyone else using Apex and having this problem? If so, 
have you determined a suitable workaround? I'm told that 
Rational knows about the problem but has no patches. Any 
suggestions?

package Test is
    type Object is tagged record
        Component : Integer;
    end record;
    type Object_Ptr is access all Object'Class;
    type My_Object is new Object with null record;

    The_Object : aliased My_Object;
    The_Ptr : Object_Ptr := The_Object'Access;
end Test;

16:35:46 >>> THE_PTR : OBJECT_PTR := THE_OBJECT'ACCESS;
16:35:46 *** THE_OBJECT is not a value of OBJECT'CLASS

Thanks in advance for any assistance.
Regards,
Paul