Wireshark mailing list archives

Re: [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string.

From: Bálint Réczey <balint () balintreczey hu>
Date: Wed, 13 May 2015 08:28:01 +0200

2015-05-13 0:26 GMT+02:00 Guy Harris <guy () alum mit edu>:


On May 12, 2015, at 3:13 PM, Evan Huus <eapache () gmail com> wrote:

Argh, one of these days I will learn to just put parentheses in rather
than taking guesses at C operator precedence :(


Yeah, the rule I've found works best for me is "if you aren't certain, throw parentheses at it".

Yes, in this case parentheses are a must.
I also llike putting them when the reader may not guess the precedence
correctly easily. This reader can be myself later ;-).

Cheers,
Balint
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://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: [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string. Evan Huus (May 12)
- Re: [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string. Guy Harris (May 12)
  - Re: [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string. Bálint Réczey (May 12)
    - Re: [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string. Graham Bloice (May 13)