Re: reference to local variable

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 2 Jan 2008 10:55:50 -0800

Message-ID:

<ORFtoDXTIHA.4440@TK2MSFTNGP06.phx.gbl>

Consider running a lint tool (PC-Lint for example) over your
codebase. When the dust settles, this should be one of the many
resolved issues I expect...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

<pauldepstein@att.net> wrote in message
news:aa26f9f8-821b-4d5f-8349-37c5659f2394@e10g2000prf.googlegroups.com...

I was reviewing some visual c++ code which appears to suffer from a
reference-to-local bug. However, I didn't see any compiler warning to
that effect. (I don't think that the warning level was the issue.)
In this code, the offending line is of the form return
(*something).somethingelse;

Could it be that the lack of transparency of the variable type is
preventing the warning? Is it the case that warnings can show up with
return x; but not with return (*something).somethingelse;

Thank you for your help,

Paul Epstein