Re: Should Inline be private in the private part of a package spec?

["Randy Brukardt" <randy@rrsoftware.com>]

"Georg Bauhaus" <rm.dash-bauhaus@futureapps.de> wrote in message 
news:5020d1fe$0$6566$9b4e6d93@newsspool3.arcor-online.net...
...
> Yes! For example, he should be able to see whether or not
> Move can be inlined.  But this case is special and, being a special case,
> should not clutter the specification of Move in Ada.Strings.Fixed!

I agree, but only because users should not be in the business of 
declaring/defining inlining. The compiler can figure that out much better 
than any declaration can.

I want implementation-independent hints about performance in package 
specifications, not ones describing specific techniques. That is, a 
declaration that calls on subprogram X ought to be compiled for the fastest 
possible performance or for the smallest possible space or for the best 
tradeoff possible. How that's accomplished should be left up to the 
implementation. Aspects like Inline and Pack get in the way of letting the 
compiler do the best possible job. (I don't believe that either of those 
even belong in the language -- which is one reason why Janus/Ada does almost 
nothing with either of them.)

                                         Randy.