[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28551] Compiler warning introduced with closed bug #2
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #28551] Compiler warning introduced with closed bug #28506 |
Date: |
Mon, 11 Jan 2010 14:24:25 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 |
Follow-up Comment #3, bug #28551 (project lwip):
In this case, the warning was correct as the code as it was before was *not*
what I wanted: (A && (B || C)) is correct, ((A && B) || C) not - only check
the IP address if proto is the same, in this case).
> When warning levels are cranked all the way up for a given
> compiler, are you going to make changes to suppress all of the
> additional warnings?
Not always, but many warnings make sense and may easily be avoided.
Personally, I'm compiling with warnings==errors, but that's for projects with
one compiler, so saying "I'll suppress all warnings for any compiler" is not
what I want.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28551>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/