I never suggested that the inlined functions be removed, as I'm well aware
of the advantages they afford. I just found it curious that so many were
not being inlined.
I did spot checked a large number of those I forwarded to this list and
they are all valid. Many are of the form throw <stuff>; return <status
code>; or if/elseif/else statements and switch statements where each clause
has a return as well as the function return. And the one I pointed out in
XML256TableTranscoder is pointing out an assignment in an if statement.
Compiler warnings exist for a reason. I frequently enable all warnings in
applications and drivers that I work on to catch things that are caused by
poor coding practices. It makes me examine my code much closer. It's a
good habit to get into.
Don
At 12:58 PM 11/19/2001 -0800, you wrote:
>Every compiler puts out different warnings than others. Under VC++, it
>generally compiles with no warnings at the highest warning level that its
>reasonable to use. There is one higher but it is very verbose. Since
>probably no one on the team works regularly with your compiler, its unlikely
>that they will know about the warnings yours puts out. Warnings about
>inlines not being inlined are just that, warnings. Some compilers are more
>agressive than others, and there is always the possibility that some
>compilers won't inline some things, but that's no reason to give up on the
>very significant performance gains that inlines provide to those compilers
>able to handle them.
>
>Aren't most of the unreachable code warnings probably things like
>while(true){} stuff, where the compiler isn't smart enough to realize that
>you really do break out eventually and fall out of the loop?
>
>--------------------------
>Dean Roddey
>The Charmed Quark Controller
>Charmed Quark Software
>[EMAIL PROTECTED]
>http://www.charmedquark.com
>
>"If it don't have a control port, don't buy it!"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
