Some inlines in static libs, some in .inl's

Started by
0 comments, last by Ebor 16 years, 6 months ago
Hey all, I noticed recently a project I downloaded had put some of its inline function implementation in .inl's it included... but not all implementations were there. Upon further inspection, it seems that only the methods that were FORCE_INLINE'd in the header were defined in the .inl's, the rest appeared to be inside static libraries. I know methods tagged "inline" (not force) don't have to be inlined by the compiler... but my question is: Where/how would you declare/define your non-force-inlined functions such that they get put into a static library, but the force-inlined ones didn't (Visual Studio, say)?
--== discman1028 ==--
Advertisement
The whole idea behind inline is that it can't go into a static lib... inline has the compiler 'copy/paste' that code in there... if it were compiled into a static lib... it can't really do that right.

This topic is closed to new replies.

Advertisement