<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 16 Jan 2013, at 14:06, Ludo Brands wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">On 16/01/2013 13:17, Jonas Maebe wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">Are those calls before or after the method body appears in the source code? The compiler cannot inline anything for which it hasn't parsed the source code yet.<br></blockquote><blockquote type="cite"><br></blockquote>The method was implemented below the code that used it. Moving it up solved it.<br><br>Actually the "inline;' in the declaration is not really used. Removing it results in the same code. Perhaps a Hint or Warning when inline is used in the declaration could avoid these mistakes.<br></span></span></blockquote></div><br><div>Actually, the correct behaviour would be that the compiler requires that it is only specified in the interface, or both in the interface and in the implementation (I'm not sure yet what's most appropriate). Inlining is always also enabled across units and hence should have to be specified in the interface.</div><div><br></div><div><br></div><div>Jonas</div></body></html>