Re: Switch to C++11 or C++14

["Mark () verizon net" <mlandri () verizon net>]

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

> On Jun 2, 2018, at 9:53 AM, Michael Mann via Wireshark-dev <wireshark-dev () wireshark org> wrote:
>
> 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?
>  
>  
>  
> -----Original Message-----
> From: Michał Łabędzki <michal.tomasz.labedzki () gmail com>
> To: Developer support list for Wireshark <wireshark-dev () wireshark org>
> Sent: Fri, Jun 1, 2018 5:21 pm
> Subject: [Wireshark-dev] Switch to C++11 or C++14
>
> Hello,
>
> Is there (still) a problem to switch to C++11 or C++14? Petri-Dish seems to support it for Windows, but there is old 
> standard used for Ubuntu.
> ___________________________________________________________________________ Sent via: Wireshark-dev mailing list 
> <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: 
> https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark 
> org?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe