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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,4885c546f6ddc77a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.219.170 with SMTP id pp10mr10670396pbc.1.1340556717251;
        Sun, 24 Jun 2012 09:51:57 -0700 (PDT)
Path: 
 l9ni15086pbj.0!nntp.google.com!news2.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: sbelmont700@gmail.com
Newsgroups: comp.lang.ada
Subject: Re: Dynamic accessibility
Date: Sun, 24 Jun 2012 09:51:56 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <ff9d9547-a61f-454e-8804-1e4f8018dac7@googlegroups.com>
References: <d2894d55-cb84-461c-8b82-da32093eda4b@googlegroups.com>
 <jrvpvs$349$1@munin.nbi.dk>
 <192bee3d-c0d4-421d-b5f6-676bce2a38db@googlegroups.com>
 <js2j2r$aj6$1@munin.nbi.dk>
NNTP-Posting-Host: 206.53.78.59
Mime-Version: 1.0
X-Trace: posting.google.com 1340556717 15074 127.0.0.1 (24 Jun 2012 16:51:57
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sun, 24 Jun 2012 16:51:57 +0000 (UTC)
In-Reply-To: <js2j2r$aj6$1@munin.nbi.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=206.53.78.59;
 posting-account=ShYTIAoAAABytvcS76ZrG9GdaV-nXYKy
User-Agent: G2/1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-06-24T09:51:56-07:00
List-Id: <comp.lang.ada>

On Friday, June 22, 2012 4:03:35 PM UTC-4, Randy Brukardt wrote:
> Note that "aliased" parameters help a bit here (they're=20
> guaranteed to live as long as the result of the function call, which is a=
=20
> bit longer than a "normal" parameter).

Since there is an active topic about it, what exactly is the distinction be=
tween explicitly aliased parameters for functions and those of procedures? =
 The way I read the LRM 6.1 (and from what I glean elsewhere), either a pro=
cedure or a function can have an E.A.P, and that your mention of 'function =
call' is assumed to mean 'subprogram call' in general.

However, the rules in 3.10.2 also vauge.  7/3 says "Other than for an expli=
citly aliased parameter...", so that parameter rule does not apply to EAPS =
of either functions or procedures.  13.3/3 deals specifically with function=
s, as does 19.2/3, and so nothing seems to explicitly apply to the EAP of a=
 procedure.

Is there some other rule that applies by default, or is 'function' assumed =
to mean both (which I don't recall happening elsewher in the LRM, but I of =
course am not that familiar with it).

-sb