Can we work unicode (UTF-8) support into these new string functions?
It's something we've been meaning to get around to and I just figured
this might be a good place to start.
On Fri, Mar 27, 2009 at 11:05:46PM +0000, gerald@xxxxxxxxxxxxx wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27872
>
> User: gerald
> Date: 2009/03/27 04:05 PM
>
> Log:
> Add initial support for string buffers - ep_allocated, growable strings
> similar to GLib's GStrings. Use them to create the list of TCP flags.
>
> Directory: /trunk/epan/dissectors/
> Changes Path Action
> +9 -11 packet-tcp.c Modified
>
> Directory: /trunk/doc/
> Changes Path Action
> +9 -2 README.developer Modified
> +12 -0 README.malloc Modified
>
> Directory: /trunk/epan/
> Changes Path Action
> +153 -0 emem.c Modified
> +82 -0 emem.h Modified
> +7 -0 libwireshark.def Modified
>
> ___________________________________________________________________________
> Sent via: Wireshark-commits mailing list <wireshark-commits@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-commits
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
> mailto:wireshark-commits-request@xxxxxxxxxxxxx?subject=unsubscribe
