diff options
author | Guy Harris <guy@alum.mit.edu> | 2010-05-24 06:06:17 +0000 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2010-05-24 06:06:17 +0000 |
commit | 1b444c55fdca784c7fea44b48c99db62cfd4069d (patch) | |
tree | badbce952d73c0fca99d071d0db5526ebe93b29b /doc/README.developer | |
parent | 19f350b9f4c2afd403a3c292d2d6b0421ae27555 (diff) | |
download | wireshark-1b444c55fdca784c7fea44b48c99db62cfd4069d.tar.gz |
Refer to the endianness arguments as "encoding" rather than
"representation" - we already use "representation" to refer to the text
representation of fields.
Change some routines with an endianness argument to make it a
representation argument instead;
svn path=/trunk/; revision=32929
Diffstat (limited to 'doc/README.developer')
-rw-r--r-- | doc/README.developer | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/README.developer b/doc/README.developer index c97bf6d77a..a94f24028a 100644 --- a/doc/README.developer +++ b/doc/README.developer @@ -2003,7 +2003,7 @@ There are several functions that the programmer can use to add either protocol or field labels to the proto_tree: proto_item* - proto_tree_add_item(tree, id, tvb, start, length, representation); + proto_tree_add_item(tree, id, tvb, start, length, encoding); proto_item* proto_tree_add_none_format(tree, id, tvb, start, length, format, ...); @@ -2235,10 +2235,10 @@ proto_register_*() function) and a value. The value will be fetched from the tvbuff by proto_tree_add_item(), based on the type of the field and, for integral and Boolean fields, the byte order of the value; the byte order, for items for which that's relevant, is specified by the -'representation' argument, which is REP_LITTLE_ENDIAN if the value is +'encoding' argument, which is REP_LITTLE_ENDIAN if the value is little-endian and REP_BIG_ENDIAN if it is big-endian. If the byte order is not relevant, use REP_NA (Not Applicable). In the future, other -elements of the representation, such as the character encoding for +elements of the encoding, such as the character encoding for character strings, might be supported. Now that definitions of fields have detailed information about bitfield |