Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 11860] Display filter operator != not working as exepected

Wireshark-bugs: [Wireshark-bugs] [Bug 11860] Display filter operator != not working as exepected

Date: Wed, 16 Dec 2015 19:16:26 +0000

What	Removed	Added
CC		joao.valverde@tecnico.ulisboa.pt

Comment # 6 on bug 11860 from João Valverde

Consistency is important because it improves usability. In this case it just
creates an awkward gotcha. Seems like a wart to me but maybe I'm missing some
background.

The most natural formal interpretation would be an AND relation, which the
operator doesn't follow anyway, for convenience.

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 11860] New: Display filter operator != not working as exepected
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 11900] Visual C++ Runtime Library Error "The application has requested the Runtime to terminate it in an unusual way." when you do not wait until Conversations is completely updated before applying "Limit to display filter"
Next by Date: [Wireshark-bugs] [Bug 11547] Feature request: highlight one byte at a time in packet bytes panel
Previous by thread: [Wireshark-bugs] [Bug 11860] Display filter operator != not working as exepected
Next by thread: [Wireshark-bugs] [Bug 11860] Display filter operator != not working as exepected
Index(es):
- Date
- Thread