ifany one following this post I replied the answer on link given above
"Inline functions should be your choice because.
1.It avoid function calling overhead.
2. variables push/pop on the stack overhead is avoided during function call
3. No return call from a function to other function which is again an overhead
4.no linker complaining happen when include at mutiple places."
------
below is argument why normal functions are not choice .
"If any one interested and against the argument of using inline function of my previous reply let just see how normal function works.
For normal function call the program stores memaddr of instructions when u call a func. It loads the function into the memory then copies parameter values and jumps to the memory location of function you r calling.
Now it run the function codes and stores the function return valu, and then jump back to the location from where function was invoked.
This is huge much run time overhead of normal function.
ifanyonefollowing this post I repliedthe solutionon link givenon top of
"Inline functionsought tobe yourselectionas a result of.
1.It avoidperformvocationoverhead.
2. variables push/pop on the stack overhead is avoidedthroughoutcall
3. Nocome backdecisionfrom aperformtodifferentperformthatisonce moreAssociate in Nursingoverhead
4.no linkercomplaintivehappenonceembodyat mutiple places."
------
below is argument whytraditionalfunctionsdon't seem to beselection.
"Ifanyoneinterested and against the argument ofvictimisationinlineperformof my previous reply letsimplyseehowevertraditionalperformworks.
Fortraditional{functiondecision|call} the program storesletteraddr ofdirectionsonceu call a func. Ithundredstheperforminto the memory then copies parameter values and jumps to the memory location ofperformyou rvocation.
Now it run theperformcodes and stores theperformcome backvalu,thenjump back tothe placementfromwhereverperformwas invoked.
This isvastabundantrun time overhead oftraditionalperform
if someone following this put up I answered the answer on link given above
"Inline features should be your desire because.
1.It avoid characteristic calling overhead.
2. variables push/pop at the stack overhead is prevented throughout feature name
3. No go back call from a feature to different function that is again an overhead
4.no linker complaining manifest when consist of at mutiple locations."
------
under is argument why everyday features aren't desire .
"If anyone fascinated and against the argument of the usage of inline feature of my preceding respond let just see how normal function works.
For normal function call this system shops memaddr of instructions when u call a func. It hundreds the characteristic into the memory then copies parameter values and jumps to the reminiscence place of characteristic you r calling.
Now it run the feature codes and shops the function return valu, after which leap lower back to the area from in which characteristic became invoked.
that is large plenty run time overhead of normal function
ifany one following this post I replied the answer on link given above
"Inline functions should be your choice because.
1.It avoid function calling overhead.
2. variables push/pop on the stack overhead is avoided during function call
3. No return call from a function to other function which is again an overhead
4.no linker complaining happen when include at mutiple places."
------
below is argument why normal functions are not choice .
"If any one interested and against the argument of using inline function of my previous reply let just see how normal function works.
For normal function call the program stores memaddr of instructions when u call a func. It loads the function into the memory then copies parameter values and jumps to the memory location of function you r calling.
Now it run the function codes and stores the function return valu, and then jump back to the location from where function was invoked.
This is huge much run time overhead of normal function