On 23-3-2014 14:05, Markus Engel wrote:
Hi, neither gcc 4.8.1 nor clang 3.4 nor msvc 12 produce this warning, so I think this might be a false positive that has been fixed in newer compiler versions. I don't see how _b[1] could be not initialized...
Thanks for checking with newer compilers.
Here's the warning I currently like best: ../../trunk/src/gradient-drag.cpp:2390:69: warning: variable 'p' is uninitialized when used within its own initialization [-Wuninitialized] Geom::Point p = ls.pointAt(ls.nearestPoint(dragger->point + p));
My goodness, what a terrible bug. Fixed in rev. 13186.
Does everybody now see why warnings are important?! Yes newer compilers may throw more warnings, but they are *better* warnings and we *need* to error on them, *by default*.
Thanks, Johan