diff options
| author | gram <gram@f5534014-38df-0310-8fa8-9805f1628bb7> | 2000-03-12 04:48:32 +0000 |
|---|---|---|
| committer | gram <gram@f5534014-38df-0310-8fa8-9805f1628bb7> | 2000-03-12 04:48:32 +0000 |
| commit | 929f70ac0b14506508e6de9dc357608b91667120 (patch) | |
| tree | 0b5f52ee7613baacc77f73697eb895592aa6a137 /packet-radius.c | |
| parent | 45942c1c41dfad28ac1aeca038e69c888d9a95c4 (diff) | |
Break proto_tree_add_item_format() into multiple functions:
proto_tree_add_protocol_format()
proto_tree_add_uint_format()
proto_tree_add_ipxnet_format()
proto_tree_add_ipv4_format()
proto_tree_add_ipv6_format()
proto_tree_add_bytes_format()
proto_tree_add_string_format()
proto_tree_add_ether_format()
proto_tree_add_time_format()
proto_tree_add_double_format()
proto_tree_add_boolean_format()
If using GCC 2.x, we can check the print-format against the variable args
passed in. Regardless of compiler, we can now check at run-time that the
field type passed into the function corresponds to what that function
expects (FT_UINT, FT_BOOLEAN, etc.)
Note that proto_tree_add_protocol_format() does not require a value field,
since the value of a protocol is always NULL. It's more intuitive w/o the
vestigial argument.
Fixed a proto_tree_add_item_format-related bug in packet-isis-hello.c
Fixed a variable usage bug in packet-v120.c. (ett_* was used instead of hf_*)
Checked in Guy's fix for the function declearation for proto_tree_add_text()
and proto_tree_add_notext().
git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@1713 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'packet-radius.c')
| -rw-r--r-- | packet-radius.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/packet-radius.c b/packet-radius.c index e0ce3ae05f..0adfba4383 100644 --- a/packet-radius.c +++ b/packet-radius.c @@ -1,7 +1,7 @@ /* packet-radius.c * Routines for RADIUS packet disassembly * - * $Id: packet-radius.c,v 1.6 1999/12/02 23:25:29 gram Exp $ + * $Id: packet-radius.c,v 1.7 2000/03/12 04:47:48 gram Exp $ * * Ethereal - Network traffic analyzer * By Johan Feyaerts @@ -584,13 +584,13 @@ proto_tree radius_tree = proto_item_add_subtree(ti, ett_radius); - proto_tree_add_item_format(radius_tree,hf_radius_code, offset, 1, + proto_tree_add_uint_format(radius_tree,hf_radius_code, offset, 1, rh.rh_code, "Packet code:0x%01x (%s)",rhcode, codestrval); - proto_tree_add_item_format(radius_tree,hf_radius_id, offset+1, 1, + proto_tree_add_uint_format(radius_tree,hf_radius_id, offset+1, 1, rh.rh_ident, "Packet identifier: 0x%01x (%d)", rhident,rhident); - proto_tree_add_item_format(radius_tree, hf_radius_length, + proto_tree_add_uint_format(radius_tree, hf_radius_length, offset+2, 2, (guint16)rhlength, "Packet length: 0x%02x(%d)",rhlength,rhlength); |