signed vs unsigned comparison warnings

[Richard Kenner]

    I'm not aware of a single bug fixed by the boatloads of changes to
    eliminate signed vs unsigned comparison warnings.  

I think I remember one ...

    As a result, I think it is in our best interest to not try and "fix"
    such warnings and instead turn off the warnings on the command line.
    We've got bigger fish to fry IMHO.

Yes and no.  These warnings tend to produce a more "strictly typed"
program and that's a good thing from a cleanliness point of view.  So
there is *some* advantage, though I agree it's not very large.