aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2001-02-23 07:17:07 +0000
committerGuy Harris <guy@alum.mit.edu>2001-02-23 07:17:07 +0000
commit3b5ef0b696d773fccafd98522b45c192de2cb858 (patch)
treefc2d9453268e04bef2b274f50a443abc1482e2fd /doc
parentc1764ee28db52ab666e6fbd0db15fa92113f7c3d (diff)
downloadwireshark-3b5ef0b696d773fccafd98522b45c192de2cb858.tar.gz
wireshark-3b5ef0b696d773fccafd98522b45c192de2cb858.tar.bz2
wireshark-3b5ef0b696d773fccafd98522b45c192de2cb858.zip
Update the documentation to correctly reflect the way tests on Boolean
fields work in display filters. svn path=/trunk/; revision=3069
Diffstat (limited to 'doc')
-rw-r--r--doc/ethereal.pod.template18
-rw-r--r--doc/tethereal.pod.template18
2 files changed, 16 insertions, 20 deletions
diff --git a/doc/ethereal.pod.template b/doc/ethereal.pod.template
index 7b63215146..e31b8db7a7 100644
--- a/doc/ethereal.pod.template
+++ b/doc/ethereal.pod.template
@@ -773,19 +773,17 @@ The following three display filters are equivalent:
frame.pkt_len > 012
frame.pkt_len > 0xa
-Boolean values are either true or false. However, a boolean field is
-present in a protocol decode only if its value is true. If the value is
-false, the field is not presence. You can therefore check the truth
-value of a boolean field by simply checking for its existence, that is,
-by naming the field. For example, a token-ring packet's source route
-field is boolean. To find any source-routed packets, the display filter
-is simply:
+Boolean values are either true or false. In a display filter expression
+testing the value of a Boolean field, "true" is expressed as 1 or any
+other non-zero value, and "false" is expressed as zero. For example, a
+token-ring packet's source route field is boolean. To find any
+source-routed packets, a display filter would be:
- tr.sr
+ tr.sr == 1
-Non source-routed packets can be found with the negation of that filter:
+Non source-routed packets can be found with:
- ! tr.sr
+ tr.sr == 0
Ethernet addresses, as well as a string of bytes, are represented in hex
digits. The hex digits may be separated by colons, periods, or hyphens:
diff --git a/doc/tethereal.pod.template b/doc/tethereal.pod.template
index 298afa81eb..6deb5f3eda 100644
--- a/doc/tethereal.pod.template
+++ b/doc/tethereal.pod.template
@@ -267,19 +267,17 @@ The following three read filters are equivalent:
frame.pkt_len > 012
frame.pkt_len > 0xa
-Boolean values are either true or false. However, a boolean field is
-present in a protocol decode only if its value is true. If the value is
-false, the field is not presence. You can therefore check the truth
-value of a boolean field by simply checking for its existence, that is,
-by naming the field. For example, a token-ring packet's source route
-field is boolean. To find any source-routed packets, the read filter
-is simply:
+Boolean values are either true or false. In a read filter expression
+testing the value of a Boolean field, "true" is expressed as 1 or any
+other non-zero value, and "false" is expressed as zero. For example, a
+token-ring packet's source route field is boolean. To find any
+source-routed packets, a read filter would be:
- tr.sr
+ tr.sr == 1
-Non source-routed packets can be found with the negation of that filter:
+Non source-routed packets can be found with:
- ! tr.sr
+ tr.sr == 0
Ethernet addresses, as well as a string of bytes, are represented in hex
digits. The hex digits may be separated by colons, periods, or hyphens: