Wireshark mailing list archives
Re: ew function(s) proto_tree_new_item_get_val_..()
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Wed, 12 Jan 2011 22:04:28 +0100
Hi, -1. It adds bloat to the API, adding noting really. Thanks, Jaap On 01/12/2011 08:51 PM, Anders Broman wrote:
Hi, Wouldn't it be handy to have a proto_tree_new_item_get_val_ which would return the value thus avoiding to having do tvb_get_.. in conjunction with proto_tree_new_item() when the value is needed in a dissector? Would an function per field type be necessary? like proto_tree_new_item_get_val_int32, proto_tree_new_item_get_val_uint32 etc or is there a smarter way of doing it? Any one interested in implementing it? Regards Anders
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- ew function(s) proto_tree_new_item_get_val_..() Anders Broman (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Jaap Keuter (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Anders Broman (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Jaap Keuter (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Anders Broman (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Jeff Morriss (Jan 13)
- Re: ew function(s) proto_tree_new_item_get_val_..() Anders Broman (Jan 13)
- Re: ew function(s) proto_tree_new_item_get_val_..() Anders Broman (Jan 12)
- Re: ew function(s) proto_tree_new_item_get_val_..() Jaap Keuter (Jan 12)