Why is not inlining that bad?

[0ffh]

Walter Bright wrote:
> Inlining a function, besides getting rid of the function call/return 
> code, which can be significant, also enables interprocedural 
> optimizations: register assignment, common subexpressions, constant 
> folding, etc. It can result in dramatically fewer instructions being 
> executed. Besides, it is more code memory cache friendly.

Reminds me of:

news://news.digitalmars.com:119/fdpmra$14n3$1@digitalmars.com

Am I lucky when I, as BCS so elegantly put it, "say my prayers to the
deities of optimization", and hope that debugfln(...){} will be reduced
to even less than call/retn?

Regards, frank