29 Oct
2013
29 Oct
'13
9:07 p.m.
2013/10/29 Johan Engelen <jbc.engelen@...2592...>:
The warning seems bogus to me, the value is certainly correctly initialized, and I've added code to check that everything that is assigned to it is also initialized. What fixes the warning is changing the first lines of that function (...)
Does that also happen if you put the assignments in an "else" branch?
I recall that GCC's control flow analysis is not perfect. For example having an if/else with a return statement in both branches could trigger a warning about missing return values.
Regards, Krzysztof