Re: Excessive Inlining
JohnQ wrote:
Then either get a better client, or do what the other poor unfortunate
OE users do to quote correctly.
What purpose would it serve?
Nonsense, C++ would be pretty neutered without inlining of trivial
methods. Just compare the performance of an application with inlining
off compared to the same code with it on.
--
Ian Collins.
JohnQ wrote:
"James Kanze" <james.kanze@gm ail.comwrote in message
news:1175348422 .117474.327060@ p15g2000hsd.goo glegroups.com.. .
>
Most coding guidelines I've seen ban inline functions
completely, for this reason."
>
************* (I hate it when OE refuses to quote correctly!) ***********
>
news:1175348422 .117474.327060@ p15g2000hsd.goo glegroups.com.. .
>
Most coding guidelines I've seen ban inline functions
completely, for this reason."
>
************* (I hate it when OE refuses to quote correctly!) ***********
>
OE users do to quote correctly.
Which begs the question: why is there no 'outline' keyword? Combined with
code-folding editors, it would make it easier to organize some class header
that have just a few or one outline function(s) (one file instead of 2 to
manage). Most compilers do seem to have an "outline all inline functions"
switch though.
code-folding editors, it would make it easier to organize some class header
that have just a few or one outline function(s) (one file instead of 2 to
manage). Most compilers do seem to have an "outline all inline functions"
switch though.
I agree that in general, inlining functions is bad because it increases
dependencies.
dependencies.
methods. Just compare the performance of an application with inlining
off compared to the same code with it on.
--
Ian Collins.
Comment