Wireshark mailing list archives
Re: error: logical && with non-zero constant will always evaluate as true
From: Jakub Zawadzki <darkjames-ws () darkjames pl>
Date: Thu, 3 Jan 2013 19:31:02 +0100
On Sat, Dec 29, 2012 at 10:37:42AM -0500, Evan Huus wrote:
In the meantime, I'm not really sure what the best workaround is...
What about using memchr() ? This might be little stupid, but if we avoid warning this way (in cost of some readability)... Cheers, Kuba. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: error: logical && with non-zero constant will always evaluate as true Jeff Morriss (Jan 03)
- Re: error: logical && with non-zero constant will always evaluate as true Jeff Morriss (Jan 03)
- Re: error: logical && with non-zero constant will always evaluate as true Guy Harris (Jan 03)
- Re: error: logical && with non-zero constant will always evaluate as true Jeff Morriss (Jan 04)
- Re: error: logical && with non-zero constant will always evaluate as true Guy Harris (Jan 03)
- <Possible follow-ups>
- Re: error: logical && with non-zero constant will always evaluate as true Jakub Zawadzki (Jan 03)
- Re: error: logical && with non-zero constant will always evaluate as true Jeff Morriss (Jan 03)