http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/Inline routineshttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/en-usTue, 27 Apr 2004 15:46:08 GMTTue, 27 Apr 2004 15:46:08 GMTEvNet (EvNet, Version=1.0.3243.35083, Culture=neutral, PublicKeyToken=null)<blockquote> <div>Tom Servo wrote:</div> <div>IIRC .NET decides that on its own. I think some requirements for the JIT to perform inlining was max. 32bytes of IL code, no branching, and some other stuff I can't remember. Not sure about the branching though.<br /></div> </blockquote> <br /> <br />I've seen posts saying that you can get away with&nbsp;*one* if-then-else construct in a function and still have it inlined. It's probably something to check on a case-by-case basis though .http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=4805Tue, 27 Apr 2004 15:46:08 GMThttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=48050http://channel9.msdn.com/4805/WebViewBug.aspx?EVT=0 Tom Servo wrote: IIRC .NET decides that on its own. I think some requirements for the JIT to perform inlining was max. 32bytes of IL code, no branching, and some other stuff I can't remember. Not sure about the branching though. I've seen posts saying that you can get away&#8230;jonathanh0http://channel9.msdn.com/4805/Trackback.aspxCool, thanks for the info!http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=4798Tue, 27 Apr 2004 15:04:13 GMThttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=47980http://channel9.msdn.com/4798/WebViewBug.aspx?EVT=0Cool, thanks for the info!Akaina0http://channel9.msdn.com/4798/Trackback.aspxFor me, in a (good) modern language this sort of thing should always be left to the compiler or the jitter. Write good, clean code and rely on the quality of the compiler/jitter. Otherwise you may find that your optimisations themselves cause problems when a new version of the compiler (or jitter) is released.<br /> <br /> In .Net, inlining takes place in the JIT.<br />http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=4796Tue, 27 Apr 2004 15:00:27 GMThttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=47960http://channel9.msdn.com/4796/WebViewBug.aspx?EVT=0For me, in a (good) modern language this sort of thing should always be left to the compiler or the jitter. Write good, clean code and rely on the quality of the compiler/jitter. Otherwise you may find that your optimisations themselves cause problems when a new version of the compiler (or&#8230;Cronan0http://channel9.msdn.com/4796/Trackback.aspx.Net inlines everything it can<br /> Eric (Gunnerson) has <a href="http://blogs.msdn.com/ericgu/archive/2004/01/29/64644.aspx">blogged </a>on this<br /> As has <a href="http://blogs.msdn.com/ricom/archive/2004/01/14/58703.aspx">Rico Mariani</a><br />http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=4795Tue, 27 Apr 2004 14:54:30 GMThttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=47950http://channel9.msdn.com/4795/WebViewBug.aspx?EVT=0.Net inlines everything it can Eric (Gunnerson) has blogged on this As has Rico MarianiCronan0http://channel9.msdn.com/4795/Trackback.aspxIIRC .NET decides that on its own. I think some requirements for the JIT to perform inlining was max. 32bytes of IL code, no branching, and some other stuff I can't remember. Not sure about the branching though.<br />http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=4794Tue, 27 Apr 2004 14:39:37 GMThttp://channel9.msdn.com/forums/TechOff/4793-Inline-routines/?CommentID=47940http://channel9.msdn.com/4794/WebViewBug.aspx?EVT=0IIRC .NET decides that on its own. I think some requirements for the JIT to perform inlining was max. 32bytes of IL code, no branching, and some other stuff I can't remember. Not sure about the branching though.Tom Servo0http://channel9.msdn.com/4794/Trackback.aspx