https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16232
--- Comment #7 from João Valverde <joao.valve...@tecnico.ulisboa.pt> ---
(In reply to Peter Wu from comment #6)
> I considered reuse of ftypes instead of a new type system, but ftypes seem
> to have significant overhead (memory allocations
In the TTL example I gave, and any similar use case (which covers a lot of
ground) that cost has already been paid. You're just fetching a pointer, no
memory allocations.
> and is not suitable for
> opaque types (pointers to C structures).
That would require more complex methods. I have a few ideas but check
GVariant[1] as a possible solution to this, if you're interested.
> As you mentioned, querying existing
> proto items is not cheap either, but it can also fail to be useful if
> multiple items exist. It also does not work if the tree is NULL.
Indeed the NULL tree issue (which is an optimization) is the main roadblock to
implement such an API.
[1]https://developer.gnome.org/glib/stable/glib-GVariant.html
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
