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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,50137bb64a119cfc
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-21 12:12:20 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!gestalt.direcpc.com!telocity-west!DIRECTV!sn-xit-03!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: "access constant" discriminant
Date: Fri, 21 Feb 2003 14:09:45 -0600
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <v5d20r57csb8a5@corp.supernews.com>
References: <_TO1a.14664$9y2.6601@nwrddc01.gnilink.net>
 <3CS1a.55972$2H6.1357@sccrnsc04> <3E4E9248.3E71D984@adaworks.com>
 <zwb0dJM87esk@eisner.encompasserve.org> <uu1eyluui.fsf@nasa.gov>
 <1ec946d1.0302201642.66eb93e5@posting.google.com>
 <1045839826.87966@master.nyc.kbcfp.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3719.2500
X-Complaints-To: abuse@supernews.com
Xref: archiver1.google.com comp.lang.ada:34376
Date: 2003-02-21T14:09:45-06:00
List-Id: <comp.lang.ada>

Hyman Rosen wrote in message <1045839826.87966@master.nyc.kbcfp.com>...
>Matthew Heaney wrote:
>> Access parameters carry accessibility information around, to check
>> that an object in an outer scope doesn't refer to another object in
an
>> inner scope.
>
>Do they actually carry this information around?
>I thought that the language rules just prevented
>such "inner" addresses from winding up in an
>"outer" pointer, not that the pointers themselves
>were "fat".


That's true for everything *except* access parameters. They actually are
required to carry a runtime accessibility level. (That's usually part of
the parameter, not part of the access.) That's another reason to avoid
access parameters, because they have more overhead than an in or in out
parameter.

          Randy.