http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1956
------- Comment #8 from guy@xxxxxxxxxxxx 2007-11-06 18:39 GMT -------
Yes, I changed the semantics of the operation from incorrect semantics to
correct semantics - *and* also fixed the semantics for bitwise AND for
byte-array fields in a separate checkin.
Bitwise AND is supposed to be true if *any* bit in the result of the bitwise
AND is set, and false only if *all* bits in the result of the bitwise AND are
clear. (That's how it's always worked for integral types, for example.)
The old code was buggy - it would return false if it found any byte in the
bitwise AND that didn't happen to have any bits set, even if other bytes did.
Byte boundaries are not special, so that's wrong.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.