Wireshark-dev: [Wireshark-dev] Request for RFC regarding string handling
From: Evan Huus <[email protected]>
Date: Mon, 28 Oct 2013 15:25:28 -0400
(This is not an RFC, I'm sending it more in the hopes that somebody
with more time and a better understanding will write a real RFC we can

Between bugs 5738 [1], 8382 [2], and 9323 [3] (all still open) we've
had a lot of discussions and ideas thrown about regarding how buggy
and inconsistent our string handling is.

Does anybody have (or feel like developing) a Grand Unified Theory of
Wireshark's future string handling? Michael and Guy and I took a stab
at something like this in the comments of [2] but it's a bit
disjointed and we never really came to a consensus that I recall. Does
anyone know if the switch to Qt has any affect on this (does it make
sense to adopt QStrings everywhere, for example?)

The next time one of these issues pops up I would love to know already
how we *ought* to behave.


[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5738
[2] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8382
[3] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9323