|
From: Florian K. <fl...@ei...> - 2015-04-01 19:07:14
|
On 01.04.2015 20:31, Philippe Waroquiers wrote: >> That recommendation is a manager's approach to fix compiler warnings :) > Effectively, silence a warning is not the same as fixing a warning :). My point! > (gcc usually finds this kind of things also IIRC, but not here ?). 4.8.2 and 4.9.2 did not report it. >> Come to think of it .. a really good warning here would have been: loop >> does not iterate. > I guess this implies to check the loop body to see if the loop variable > is modified or not. Yes. In general, that is undecidable. In this particular case, it'd have been elementary. Florian |