Actually it's more like the 'short_name' field in that file_type_subtybe
struct, but not exactly - the open_info ones are captialized whereas the
file_type_subtybe 'short_name' ones are lower-case.
But in my opinion they should be not only the same exact name strings, but
inside just one
BTW, is changing the wtap_register_open_info() function prototype/ABI again
soon going to cause you problems?
I ask because it changes again, with an additional argument, in here:
https://code.wireshark.org/review/#/c/431/
The additional argument is for whether the wiretap reader being
2014 18:26
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add
option to choose format type of capture file
BTW, is changing the wtap_register_open_info() function prototype/ABI again
soon going to cause you problems?
I ask
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Hadriel Kaplan
Sent: den 6 mars 2014 18:26
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add
option to choose format type of capture file
BTW, is changing
