Timeline for Inline functions in C++. What's the point?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2018 at 0:05 | comment | added | curiousguy | "every function call must now be replaced with the full code of the function" And inline function isn't a function where the call sequence is omitted and where the assembly code of the function is copied in place. An inline function is compiled in place, by bringing the high level intermediate code inline. That allows the compiler to treat the function body effectively as a clean macro (a clean macro is one that doesn't have the quirks of C preprocessor macros), with potentially many optimizations available. | |
| Jan 10, 2011 at 20:36 | comment | added | Konrad Rudolph | But the compiler can (and does!) figure this out much better than the programmer in general. So this is not a valid argument. | |
| Jan 10, 2011 at 19:11 | history | answered | Charles E. Grant | CC BY-SA 2.5 |