inline-functions

问题 See title: what does it mean for a C++ function to be inline? 回答1: The function is placed in the code, rather than being called, similar to using macros (conceptually) This can improve speed (no function call), but causes code bloat (if the function is used 100 times, you now have 100 copies) You should note this does not force the compiler to make the function inline, and it will ignore you if it thinks its a bad idea. Similarly the compiler may decided to make normal functions inline for

问题 I am asking this basic question to make the records straight. Have referred this question and its currently accepted answer, which is not convincing. However the second most voted answer gives better insight, but not perfect either. While reading below, distinguish between the inline keyword and “inlining” concept . Here is my take: The inlining concept This is done to save the call overhead of a function. It\'s more similar to macro-style code replacement. Nothing to be disputed. The inline

问题 While it would be very convenient to use inline functions at some situations, Are there any drawbacks with inline functions? Conclusion : Apparently, There is nothing wrong with using inline functions. But it is worth noting the following points! Overuse of inlining can actually make programs slower. Depending on a function\'s size, inlining it can cause the code size to increase or decrease. Inlining a very small accessor function will usually decrease code size while inlining a very large

问题 I\'m a C/C++ developer, and here are a couple of questions that always baffled me. Is there a big difference between \"regular\" code and inline code? Which is the main difference? Is inline code simply a \"form\" of macros? What kind of tradeoff must be done when choosing to inline your code? Thanks 回答1: Is there a big difference between "regular" code and inline code? Yes and no. No, because an inline function or method has exactly the same characteristics as a regular one, most important

问题 I have a function that is declared and defined in a header file. This is a problem all by itself. When that function is not inlined, every translation unit that uses that header gets a copy of the function, and when they are linked together there are duplicated. I \"fixed\" that by making the function inline, but I\'m afraid that this is a fragile solution because as far as I know, the compiler doesn\'t guarantee inlining, even when you specify the \"inline\" keyword. If this is not true,

问题 I understand that \"inline\" by itself is a suggestion to the compiler, and at its descretion it may or may not inline the function, and it will also produce linkable object code. I think that \"static inline\" does the same (may or may not inline) but will not produce linkable object code when inlined (since no other module could link to it). Where does \"extern inline\" fit into the picture? Assume I want to replace a preprocessor macro by an inline function and require that this function

问题 What is the advantages/disadvantages of using inline functions in C++? I see that it only increases performance for the code that the compiler outputs, but with today\'s optimized compilers, fast CPUs, huge memory etc. (not like in the 1980< where memory was scarce and everything had to fit in 100KB of memory) what advantages do they really have today? 回答1: Inline functions are faster because you don't need to push and pop things on/off the stack like parameters and the return address;