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-Thread: a07f3367d7,9983e856ed268154
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.236.193.73 with SMTP id j49mr11117207yhn.7.1344998912381;
        Tue, 14 Aug 2012 19:48:32 -0700 (PDT)
MIME-Version: 1.0
Path: 
 c6ni115589900qas.0!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nrc-news.nrc.ca!goblin1!goblin3!goblin.stu.neva.ru!gegeweb.org!news.ecp.fr!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Should Inline be private in the private part of a package spec?
Date: Thu, 9 Aug 2012 16:33:10 -0500
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <k01aao$jce$1@munin.nbi.dk>
References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net>
 <e416cb92-6ec8-4514-8fa9-c35d6432b117@googlegroups.com>
 <wcc4noj4zof.fsf@shell01.TheWorld.com> <jvnchp$r5c$1@munin.nbi.dk>
 <wccr4rkqed5.fsf@shell01.TheWorld.com> <op.wiml9rw3ka8ora@aspire.local>
 <502005b6$0$9510$9b4e6d93@newsspool1.arcor-online.net>
 <op.wim0pbprka8ora@aspire.local>
 <50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1344547992 19854 69.95.181.76 (9 Aug 2012 21:33:12 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Thu, 9 Aug 2012 21:33:12 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Date: 2012-08-09T16:33:10-05:00
List-Id: <comp.lang.ada>

"Georg Bauhaus" <rm.dash-bauhaus@futureapps.de> wrote in message 
news:50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net...
> On 06.08.12 23:01, Vasiliy Molostov wrote:
...
> What the program does is not a matter of whether or not
> some subprogram needs calling convention Ada or StdCall or
> some such. Hence, from the perspective of the caller,
> knowing the calling convention of an import is distraction
> at best.

The convention can make the program legal or illegal: that's surely the 
definition of something that has to be in the specification. (For example, 
taking 'Access of a C convention subprogram and assigning it to an Ada 
convention access type is illegal for obvious reasons.)

Bob's point is that Inline doesn't make the program illegal per-se, so it is 
more of a gray area. But it does affect the compilation ordering, and IMHO, 
that needs to be visible information.

                                        Randy.