osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Clarify which filter types can share the same name 

svn path=/trunk/; revision=53017
This commit is contained in:
Pascal Quantin 2013-11-01 16:00:58 +00:00
parent 9589727b3a
commit 5217ec489f
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/README.dissector
View File

@ -1009,6 +1009,14 @@ the same abbreviation. For instance, the following is valid:
This way a filter expression can match a header field, irrespective of the This way a filter expression can match a header field, irrespective of the
representation of it in the specific protocol context. This is interesting representation of it in the specific protocol context. This is interesting
for protocols with variable-width header fields. for protocols with variable-width header fields.
Note that the formats used must all belong to the same list as defined below:
- FT_INT8, FT_INT16, FT_INT24 and FT_INT32
- FT_UINT8, FT_UINT16, FT_UINT24, FT_UINT32, FT_IPXNET and FT_FRAMENUM
- FT_UINT64 and FT_EUI64
- FT_STRING, FT_STRINGZ and FT_UINT_STRING
- FT_FLOAT and FT_DOUBLE
- FT_BYTES, FT_UINT_BYTES, FT_AX25, FT_ETHER, FT_VINES, FT_OID and FT_REL_OID
- FT_ABSOLUTE_TIME and FT_RELATIVE_TIME
The HFILL macro at the end of the struct will set reasonable default values The HFILL macro at the end of the struct will set reasonable default values
for internally used fields. for internally used fields.