Wireshark-dev: Re: [Wireshark-dev] removed functions fast way to find substitutes?
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Semjon
Sent: den 21 november 2014 09:48
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] removed functions fast way to find substitutes?
>Hello,
>
>I maintain a dissector for a proprietary protocol of my employer and now and then I grab me some current wireshark-sources and check if my dissector code is still compatible which - in recent times- unfortunately often it is >not due to changes in the wireshark lib / API.
>
>So everytime my code fails to compile/link I have to check which functions were removed and which new functions do I have to use now.
>One of my current problems is with
>
>tvb_get_faked_unicode(...)
Google says https://www.wireshark.org/lists/wireshark-bugs/201401/msg00446.html :-)
>which isn't available anymore.
>In my Protocol I have some Ascii-encoded String but which comes as two bytes per character. Example:
>{0x0031, 0x0032, 0x0033, 0x0034, 0x0000} in tvb should display in GUI/Tree/PacketList as "1234"
>I used to call:
>
>tvb_get_faked_unicode(NULL,tvb, 20, ((tvb_length(tvb)-20)/2),ENC_BIG_ENDIAN)
>
>and display result as %s in col_append_fstr() or as FT_STRING in proto_tree_add_string().
>
>So could anyone give me a hint, is there a function still available for this type of encoding or do I have to write something.
>
>In general is there a fast/convenient way - other than manually looking through the sources after functions that might do what i want - to check if this function X is now replaced by function Y.
>
>Other examples I need to replace are:
>abs_time_to_ep_str()
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=237669a35deacbead9346234019c2e50544c8534
>nstime_delta()
Wsutil/nstime.h as this symbol perhaps you need to change your include ?
>
>Maybe there's some changelog containing this info?
>
>Thanks in advance.
>
>SemGo
Regards
Anders
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
