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,74dad3573c51736a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Received: by 10.68.15.41 with SMTP id u9mr2678306pbc.3.1322023162029;
        Tue, 22 Nov 2011 20:39:22 -0800 (PST)
Path: 
 lh20ni7756pbb.0!nntp.google.com!news2.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!news-transit.tcx.org.uk!aioe.org!.POSTED!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re:
 =?utf-8?B?QmFzaWMgcXVlc3Rpb25zIGFib3V0IHdvcmRpbmdzIGluIOKAnEludGVyZmE=?=
 =?utf-8?B?Y2luZyBQcmFnbWFz4oCd?=
Date: Wed, 23 Nov 2011 05:39:21 +0100
Organization: Ada @ Home
Message-ID: <op.v5dtvvs4ule2fv@douda-yannick>
References: <op.v5c0ztctule2fv@douda-yannick>
 <eb25b13e-cc4c-4dcb-9b74-1fcf379d5fee@v38g2000prh.googlegroups.com>
NNTP-Posting-Host: wgHBtatYse3YjKAUQsirEA.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/11.60 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news2.google.com comp.lang.ada:14545
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2011-11-23T05:39:21+01:00
List-Id: <comp.lang.ada>

Le Tue, 22 Nov 2011 21:07:53 +0100, Adam Beneschan <adam@irvine.com> a  =

=C3=A9crit:
>> In notes at the bottom> 46 5  The local_name in an interfacing pragma=
  =

>> can denote more
>> > than one entity in the case of overloading. Such a pragma
>> > applies to all of the denoted entities.
>>
>> Why not the same with types derived from a type with an interfacing  =

>> pragma
>> ?
>
> Types can't be overloaded.  Since you can declare more than one
> subprogram with the same name, the purpose of this note is to describe=

> what happens if you use that name in one of these pragmas, in that
> case.  There's no need for a similar rule about types.

Oops, I was misunderstood here.

Say T11 is tagged type. A pragma specify some convention for T11.  =

According to this RM page, then a type T12 extending (or not) T11, will =
 =

hold the same convention too.

Say T21 is a =E2=80=9Cclassic=E2=80=9D scalar type. A pragma specify som=
e convention for  =

T21. According to this RM page, then a `type T22 is new T21;` will not  =

hold the same convention, because it is not denoted by the same same any=
  =

more, and it is not tagged.

I am not feeling fine with this: T12 will keep the convention, while T22=
  =

won't. T22 should too.

Similarly: formally (no compiler specific answer please), what about  =

`subtype T23 is T21;`. Not denoted by the same name too, so too not  =

warranted to still hold the convention specified for T21 ? If so, this i=
s  =

another reason for me to not feeling OK.

-- =

=E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D  [Ep=
igrams on  =

Programming =E2=80=94 Alan J. =E2=80=94 P. Yale University]
=E2=80=9CStructured Programming supports the law of the excluded muddle.=
=E2=80=9D [Idem]