"Allen Smith" <AS******@hotmail.com> wrote in message
news:OD**************@TK2MSFTNGP14.phx.gbl...
I did not run any performance test.
It makes sense for me there will be additional CPU cycles to call
functions.
What makes sense is not always so. In this particular case, compilers have
been better at this than humans for the past decade or so. For at least that
long it has been a waste of time to specify inlining. In fact, doing so can
prevent some compilers from doing a good job deciding which code should be
inline.
If I write the code in all the places instead of function may be a good
approach. Just a thought.
I find that it is a very bad idea to solve problems which do not exist.
Therefore, before I optimize my code, I make sure that it works (as
non-working code is usually worse than slow code, since I don't write
horribly slow code any more). Once it works, I then look to see if there are
performance problems. If so, I then look for the solution to those problems.
It may never turn out that the solution to a performance problem involves
inlining.
John Saunders