On Fri, Oct 14, 2011 at 6:38 PM, Mark Atwood <[email protected]> wrote: > I would prefer to make the warning go away by initializing the variables.
What's the gain? Aren't uninitialized vars caught by valgrind already? Suppose a var should be initialized at some other point. If you set it to 0 in the constructor, and then forget to initialize it at that other point, valgrind no longer catches that error. > I thought -Weffc++ was not turned on. It is in drizzle-build-all-warnings. Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
