Re: Semantics of Inline vs non-Inline

["Christoph Karl Walter Grein" <AdaMagica@web.de>]

From: Wojtek Narczynski <wojtek@power.com.pl>

> > 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.

When you're going outside the recommended level of support, you're on your own and can't blame the compiler
vendor. It's a nice feature if you get a warning. And ACT is very open to proposals for better compiler messages.
(I do not know who the compiler vendor of the OP is.)

> > 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 <XXXXX>", you're supposed to provide
> correct <XXXXX>.

  function Push( Datum : Datum_Type ) return List.Cell_Ptr is
     LM_Datum : List.Datum_Type;
     for LM_Datum'Address use Datum'Address;

And here, no correct <XXXXX> is provided. So RM 13.3(13) is violated. Therefore the program is erroneous.

Erroneous means: The compiler need not detect this. If it doesn't, the program is free to do anything. The (in)famous
nasal demons :-)
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193