Library standardization

[Walter Bright]

e-t172 wrote:
> My point is, inlining functions without the developer's consent is 
> likely to cause grave problems when writing shared libraries. There 
> should be a way to tell the compiler "Hey, I want you NOT to inline this 
> function, even if that sound stupid, because I want it to be in MY 
> shared library, so I can update it whenever I want". Maybe the export 
> attribute does this already, as Bill Baxter was suggesting.

In the .di file you ship with the library,

     int foo();

will mean that foo() will never be inlined.