Printable View
-------------------------
I had a question regarding inline functions. When do you use then and how many of you use them a lot? It seems like it is more of a disadvantage because a functions code will be copied and if it is called a lot then then size of the executable will go up. Am I wrong?
Huge page on it here
Check out mainly Preludes link
My own personal technique.. is to inline my constructors and destructors.. because odds are they will probably only be called once. { generally speaking of course; } :cool:
>because odds are they will probably only be called once.
Once per creation of an object or temporary, yes. :) Also keep in mind that constructors and destructors can potentially have a lot more code than appears from the body.
You shouldn't care too much about the size of your executable. Most of it likely comes from predefined classes (especially when using visual development tools).Quote:
Originally Posted by hern
Just yesterday we (another student and I) had to optimize a given image smooth function. It was about 40 lines of code and went through the image pixel by pixel, line by line. Really clear and beautiful (as much as C can be) code.
When we were finished with it it was ugly, about 450 lines of code, full of unrolled loops, most of it almost an exact copy&paste from a few lines above. But it was about 8 times faster than the original piece of code.
Speed and size are in no way related in programming. At best it's an antiproportional relation.