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: 103376,1676be4fafed1dbb X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!proxad.net!newsfeed.tpinternet.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail From: Wojtek Narczynski Newsgroups: comp.lang.ada Subject: Re: Semantics of Inline vs non-Inline Date: Fri, 15 Oct 2004 13:02:25 +0200 Organization: tp.internet - http://www.tpi.pl/ Message-ID: References: NNTP-Posting-Host: avw170.neoplus.adsl.tpnet.pl Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: atlantis.news.tpi.pl 1097838176 2267 83.27.56.170 (15 Oct 2004 11:02:56 GMT) X-Complaints-To: usenet@tpi.pl NNTP-Posting-Date: Fri, 15 Oct 2004 11:02:56 +0000 (UTC) User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Xref: g2news1.google.com comp.lang.ada:5251 Date: 2004-10-15T13:02:25+02:00 List-Id: Hello, > The question here is not "Inline vs. not Inline", but "is 'Address attribute > guaranteed to deliver correct results". Okay. > RM 13.3(15..18) specify the recommended level of support. Those paragraphs do not mandate returning a rubbish address for unsuported cases. Also please note that if you use other attributes in context where it does not make sense, the compiler will tell you about it. > RM 13.3(13) says it's the programmer's responsibility to ensure the > address is valid. "If an Address is specified, it is the programmer's responsibility to ensure that the address is valid; otherwise, program execution is erroneous." This does not say anything about when 'Address produces correct result, it only says that in "for X'Address use ", you're supposed to provide correct . Regards, Wojtek