forked from osmocom/wireshark
Update list of field types compatible for comparisons
Change-Id: Ic356773f780b88f0a7d8735167dec240fa5bdbc2 Reviewed-on: https://code.wireshark.org/review/13670 Reviewed-by: Pascal Quantin <pascal.quantin@gmail.com>
This commit is contained in:
parent
818c274721
commit
fd52f92947
|
@ -1120,13 +1120,14 @@ for protocols with variable-width header fields.
|
|||
|
||||
Note that the formats used must all belong to the same group as defined below:
|
||||
- FT_INT8, FT_INT16, FT_INT24 and FT_INT32
|
||||
- FT_UINT8, FT_UINT16, FT_UINT24, and FT_UINT32
|
||||
- FT_UINT8, FT_UINT16, FT_UINT24, FT_UINT32, FT_IPXNET and FT_FRAMENUM
|
||||
- FT_INT40, FT_INT48, FT_INT56 and FT_INT64
|
||||
- FT_UINT40, FT_UINT48, FT_UINT56, and FT_UINT64
|
||||
- FT_STRING, FT_STRINGZ and FT_UINT_STRING
|
||||
- FT_UINT40, FT_UINT48, FT_UINT56, FT_UINT64 and FT_EUI64
|
||||
- FT_ABSOLUTE_TIME and FT_RELATIVE_TIME
|
||||
- FT_STRING, FT_STRINGZ, FT_UINT_STRING and FT_STRINGZPAD
|
||||
- FT_FLOAT and FT_DOUBLE
|
||||
- FT_BYTES and FT_UINT_BYTES
|
||||
- FT_OID and FT_REL_OID
|
||||
- FT_BYTES, FT_UINT_BYTES, FT_ETHER, FT_AX25, FT_VINES and FT_FCWWN
|
||||
- FT_OID, FT_REL_OID and FT_SYSTEM_ID
|
||||
|
||||
Any field not in a grouping above should *NOT* be used in duplicate field
|
||||
abbrevations. The current code does not prevent it, but someday in the future
|
||||
|
|
Loading…
Reference in New Issue