Re: Where are the specific WARNS=n defined?

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> It is not necessarily an error to compare signed and unsigned
>> values.  [...]
> And it is not an error to put assignments in conditionals, or not
> place parentheses to clarify operator precedence, etc.  It is a
> warning [...].  For some of us this is helpful.  The compiler writers
> try to help protect programmers against common mistakes.  If you
> don't like the warnings you are free to turn them off.

That's what I do - along with a handful of other such warnings.

The question asked what the appropriate action was, whether to turn the
warnings off (the way real kernel compiles apparently do anyway) or
uglify the code to work around the warning [ok, my phrasing].  I
believe the former is better, because in my experience the mistake the
warning warns about is anything but common.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B