Re: [Valgrind-users] Uninitialized access findings on non-static file scope variables that's been initialized?

[Jeffrey W. <nol...@gm...>]

On Thu, Aug 13, 2015 at 12:06 PM, Dan Kegel <da...@ke...> wrote:
> On Thu, Aug 13, 2015 at 6:11 AM, Jeffrey Walton <nol...@gm...> wrote:
>> Al we have managed to do since C++98 (maybe earlier) is move the
>> problem around because the C++ language has not given us the tools we
>> need to address the problem.
>
> What part of "stop doing that" does C++ get in the way of?

The objects simply exist, and telling someone "don't do that" is
wishful thinking at best. That's the implicit bikeshedding I was
talking about.

And converting the file-scoped globals into locals with accessors
suffers the same problem on the destructor side. So the problem was
not fixed; rather it was just moved around.

Jeff