Sign comparison warnings are the largest class of warnings remaining. These commits fix many of the warnings -- which were indeed valid.
The commits were broken up to make reviewing easier.
Sign comparison warnings are the largest class of warnings remaining. These commits fix many of the warnings -- which were indeed valid.
The commits were broken up to make reviewing easier.
Noticed when sign-comparison warnings were enabled.
foo.size() typically returns an unsigned integral type; make loop variables
match those types' signedness.
ACK
Is this enough to remove -Wno-sign-compare from the build? Or are there still a lot of these warnings left even after this?
Still too many left in the headers, to remove -Wno-sign-compare. Several key classes exported directly to the network assign and test 'unsigned int' types against -1. A few other warnings require some thinking as well. My patches get 75% of the warnings maybe.
ACK