"STATEMENTS IN THE FUNCTION ARE SUBSTITUTED WHENEVER THE FUNCTION IS CALLED."
This is very true, but the only thing on the stack would be automatic variables in the function. The function itself is turned into machine (or intermediate) code when compiled. It can expand the size of the translation unit's object code significantly, but you eliminate the overhead of a function call, including all the stack pushing and popping that goes on. In any case, these functions can be very large, but for best effect, keep them as small as possible. This is why in C++ classes, inline methods are generally small getter/setter or other trivial functions. Others should be implemented in the source file instead of the class definition header file. This is a trade off between speed and size. If the function is large and/or complex, then the function call overhead is probably only a small part of the total time taken to execute it.
One final thing, statements are inserted into the function when compiled, not when it is called. :-)
Hi. I have a form with list box : lst_product, datagridview : grd_order and button: btn_addline. lst_product has a list of product ids selected from database (MS Acess 2013) , grd_order is by default empty except for 2 headers and btn_addline adds rows to grd_order.
Hi, as I was told that my code doesn’t scale well at all, I thought perhaps I’d try to get a better understanding of interfaces/abstract classes and classes and the relationship between them.
I don’t want at this stage work on a big separate project as I've already got plenty ...
I am writing a java program that needs to execute shell commands, so I wrote a function that would take the command to execute as a string (ie: "mkdir ~/Folder1") and execute that command with the shell. Here is the function:
Runtime run = Runtime.getRuntime();
Process pr = ...