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,af42f89f2159f3b6
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: A note on GNAT 3.05 performance
Date: 1996/06/28
Message-ID: <Dtpny6.72C@world.std.com>#1/1
X-Deja-AN: 162559384
references: <dewar.835245019@schonberg> <4qeubm$8th@linus.mitre.org>
 <DtF35x.5D@jvdsys.nextjk.stuyts.nl> <dewar.835605407@schonberg>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-06-28T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <dewar.835605407@schonberg>, Robert Dewar <dewar@cs.nyu.edu> wrote:
>If you want something passed by reference and your code depends on it,
>either use an access parameter (if the value is guaranteed to be non-null)
>or an explicit access type. This is the only legitimate way to be sure
>that a record is passed by reference.

6.2 lists several cases where you are guaranteed to get pass-by-ref:
tagged types, limited records, etc.

In most cases, I prefer the explicitness of access types, though (either
access parameters or named access types, as appropriate).

- Bob