| Hope no one minds a little unsolicited input.
Moving to c++ or at least supporting c++ module builds during main build could greatly improve data serialization and deserialization by using Google Protocol Buffers (protobuf). For example, I have a custom tshark build that uses protobuf to serialize data from epan dissect tree, export data from tshark, and then unserialize detailed dissection tree data in another application.
I had earlier versions of similar code that used pdml or my own binary serialization routines to export detailed dissection data. The protobuf version is by far the best approach in terms of speed and memory. It’s a LOT better!
I’ve been thinking about incorporating into dissection process but haven’t had cycles. Not a small job. Sent from my iPhone
What features of C++11 and 14 do you plan to use and where? I know we've had the C vs C++ discussion before and I'd still vote for keeping things where they are as far as "GUI" is C++ and epan + dissectors (i.e. libwireshark) as C. I'm a little more indifferent to the "peripherals"/tools. Other than some "shorthand" in syntax, I don't see the necessity to "upgrade". Are we missing out on some Qt features because of no C++ 11 support?
|
