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=0.6 required=5.0 tests=BAYES_20,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9640b17421044f1a
X-Google-Attributes: gid103376,public
From: Thomas Handler <thandler@systems.at>
Subject: Re: accesibility level problem
Date: 1999/02/22
Message-ID: <36D14974.EBF4B28E@systems.at>#1/1
X-Deja-AN: 447059770
Content-Transfer-Encoding: 7bit
References: <36CD206A.32D96489@systems.at> <36CDE45C.5B5E04D8@lmco.com>
 <36D06C0F.32CA8C6B@umundum.vol.at> <7aqd0i$tt5$1@nnrp1.dejanews.com>
Content-Type: text/plain; charset=us-ascii
Organization: SYSTEMS AG
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-02-22T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert and Steve,

once again a great "Thank you" for bringing in some light.

As Robert pointed out, I already knew (after some trials) that the error
message disappears when declaring the access type locally.
Though having read the RM 3.10.2 forth and back several times it was not
clear to me why I got the error message.
Steve's hint with the possibility of 'chaining' the access brought me
back on track! and Robert was right when saying that the pure
Information in the RM doesn't help you out of the dark ;-)

Thomas Handler