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,9640b17421044f1a
X-Google-Attributes: gid103376,public
From: Thomas Handler <th@umundum.vol.at>
Subject: Re: accesibility level problem
Date: 1999/03/02
Message-ID: <36DC4283.68ECFA50@umundum.vol.at>#1/1
X-Deja-AN: 450454328
Content-Transfer-Encoding: 7bit
References: <36CD206A.32D96489@systems.at> <36CDE45C.5B5E04D8@lmco.com>
 <7alc7m$uo2$1@nnrp1.dejanews.com> <wccr9r99jge.fsf@world.std.com>
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: news@ip-plus.net
X-Trace: pollux.ip-plus.net 920401299 27968 194.183.134.207 (2 Mar 1999
 19:01:39 GMT)
Organization: Toemmsn's Homeoffice
Mime-Version: 1.0
NNTP-Posting-Date: 2 Mar 1999 19:01:39 GMT
Newsgroups: comp.lang.ada
Date: 1999-03-02T19:01:39+00:00
List-Id: <comp.lang.ada>

Robert A Duff wrote:
> 
Robert,

> I think the original poster wondered why it was all based on the access
> type, and not on the object.  The problem is that the object declaration
> doesn't contain any information about where the thing points, and we
> didn't want to do it all with run-time checks (although Tucker invented
> access parameters fairly late in the game, and they allow a limited form
> of run-time checking).

This is exactly where my problem was buried - I knew I had the
dependance on the access type but it was not clear for me why - I even
wasn't able to read this info the right way fro the ARM...

Thomas Handler