Re: Child vs nested package : efficiency matter

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Tue, 01 Jun 2010 17:03:44 +0200, Adam Beneschan <adam@irvine.com> a  
écrit:
> I can't say anything about any particular compiler.  One possibility:
> if procedure A calls procedure B, and A and B are in the same source,
> a compiler may be able to put the code of B inline in procedure A's
> code---i.e. the code for A will include B's code, rather than
> including a "call" instruction.  If it does this, then in the process,
> it may also to be able to eliminate instructions in B's code that have
> no effect on A.  It's a lot harder to do this if A and B are in
> different sources, which I'm assuming is happening if you are pulling
> code out of a nested package and putting it in a child package.
Adam, I've thought about it at that moment, so I've added some pragma  
Inline for the relevant subprograms in the packages specs. This did not  
change anything.

Do you think there are some reasons to believe pragma Inline is not  
properly applied with inter-package subprograms invocations ?

-- 
There is even better than a pragma Assert: a SPARK --# check.
--# check C and WhoKnowWhat and YouKnowWho;
--# assert Ada;
--  i.e. forget about previous premises which leads to conclusion
--  and start with new conclusion as premise.