Am 24.11.2011 00:27, schrieb Jérôme Gardou:
Truncating it explicitly tells it "yes, I truncate this value, not for
avoiding compiler warning, but because that's what I want". See r54460
to see which kind of bugs such checkers could help to fix.
What's next?
(Value & 0xFFFF) -> warning because ANDing an ULONG64 is regarded as
"silencing a warning" -> fix:
__really_truncate_this_unsigned_int64_to_ushort_and_discard_lost_bits(Value);
?
For me casting *is* already doing it "explicitly". And if someone
doesn't know that casting is the same as truncating, he shouldn't do C
coding.
I agree with Aleksey: turn this feature off, its a bit too much.
Timo
_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev
