Wireshark-bugs: [Wireshark-bugs] [Bug 11860] Display filter operator != not working as exepected
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 17 Dec 2015 05:37:57 +0000

Comment # 16 on bug 11860 from 
(In reply to Guy Harris from comment #13)
> ...and "contains", "matches", and "bitwise_and", to name three *more*
> relational operators.
> 
> Now, perhaps what we could do is make the set of relational operators be =,
> <, <=, >, >=, "contains", "matches", and "bitwise_and", with *all* of them
> meaning "there exists an instance of field {field} where...", and allow
> *any* relational operator to be prefixed by "!", with "!{op}" meaning "for
> all instances of {field}, the relation '{value of that instance of the
> field} {op} {value}' is *false*".
> 
> That doesn't allow a "there exists an instance of {field} for which the
> relation '{value of that instance of the field} is not equal to {value}",
> but we could steal the <> operator from Pascal and have that mean "is not
> equal to".  (And, yes, you could do "{field} !<> {value}", which means "for
> all instances of {field}, the value of that instance of the field is not
> unequal to {value}", i.e. "all instances of {field} have the value {value}".

It's a really nice idea and very promising but then '!>' is logically different
to '<='. Not a showstopper IMO.

How about just using '<>' as a shorthand for !({field} == {value})?

Simpler and good enough? It would serve my needs just fine.

You are receiving this mail because:
  • You are watching all bug changes.