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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,63ed09fc54092c73
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.66.72.7 with SMTP id z7mr1831621pau.15.1359807872117;
        Sat, 02 Feb 2013 04:24:32 -0800 (PST)
X-Received: by 10.50.154.193 with SMTP id vq1mr165350igb.4.1359807871888; Sat,
 02 Feb 2013 04:24:31 -0800 (PST)
Path: 
 6ni27960pbd.1!nntp.google.com!ld4no15295335pbb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 2 Feb 2013 04:24:31 -0800 (PST)
In-Reply-To: <18239154-6753-455c-b00e-4caf876e03ff@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=114.145.158.199;
 posting-account=Mi71UQoAAACnFhXo1NVxPlurinchtkIj
NNTP-Posting-Host: 114.145.158.199
References: <6d66d1c4-ed22-446b-a9d7-dc806ae1ef8f@googlegroups.com>
 <f4d3708d-d17c-4e53-8f45-f9ac6f64ee54@googlegroups.com>
 <coikrsq8nv3b$.1xcqe2olg7bpv$.dlg@40tude.net>
 <5ab43474-0ce2-425c-836b-ff4c97587958@googlegroups.com>
 <8f7b509f-c92d-48b0-8322-cdc48baf4846@googlegroups.com>
 <18239154-6753-455c-b00e-4caf876e03ff@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3f6b84d2-6fee-43ca-ac80-fb99c0778a47@googlegroups.com>
Subject: Re: When is a rename not a rename?
From: ytomino <aghia05@gmail.com>
Injection-Date: Sat, 02 Feb 2013 12:24:32 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2013-02-02T04:24:31-08:00
List-Id: <comp.lang.ada>

On Saturday, February 2, 2013 10:40:40 AM UTC+9, Adam Beneschan wrote:
> Although the two Operation's that could be denoted by this actually refer=
 to the same declaration after renaming is considered, it's still ambiguous=
 since we don't know what should be passed for Offset.  Parameter names can=
 also be different in a subprogram rename, which can pose another problem. =
 The language rules would have to be written to allow the case you're inter=
ested in but disallow examples like mine.  Not easy.

Right you are. I'm afraid for/have to be careful not to make typo in renami=
ng.

I think... in the case, human have not to write "renames" by hand. Actually=
, There are some typo in examples (including mine...orz) presented in this =
thread. :-)

"Integrated" nested packages proposed in AI05-0135 seems easy and good to m=
e.

with XXX;
package YYY is=20
   use package <Included_XXX> renames XXX;
end YYY;

with Small1, Small2;
package Large is
   use package <Included_Small_1> renames Small1;
   use package <Included_Small_2> renames Small2;
end Large;

Perhaps, it too makes large headers like Win32Ada more simpler.

As another solution, I have to remove "use type" from client code because "=
use" implies "use type". But I have to remove "use type" from other person'=
s code...