Warning in cases in which the compiler doesn't know whether something is correct or not, is stupid in any case IMO, unless it's some --enable-uber-pedantic-warnings compiler flag. It could as well say "warning: your code could be wrong" and by chance this might be true.
Dmitry Gorbachev wrote:
Notice that the warning is "may be used uninitialized" and not "is used uninitialized", so it is correct, in a sense.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev