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

[Michał Łabędzki <michal.tomasz.labedzki () gmail com>]

Just right. I assume that C++ is for UI, but in fact, it may be used
also for dissectors, etc. You have my vote for "C++ for Qt5 GUI" and
"C for the rest". I only think about C++11 together with Qt5. Qt4 was
dropped so there is an occasion to standardize what standard of C++ we
use. I use C++11 feature - list initialization [1]. My setup of
Wireshark allow that because CMake set is as "-std=gnu++11", however,
Petri-Dish fails on Ubuntu because of old "-std=gnu99". I do not know
how it works because gnu99 is c99 + gnu extensions, but it is also C,
not C++ (are there "reference&" for C?).

I think the best solution is to switch to C++11. I hope gnu++11 is not
required by Qt 5.7 or newer and this also can be changed to c++11.

[1] https://buildbot.wireshark.org/petri-dish/builders/Ubuntu%20Petri%20Dish%20x64/builds/3837/steps/compile/logs/stdio
sob., 2 cze 2018 o 15:53 Michael Mann via Wireshark-dev
<wireshark-dev () wireshark org> napisał(a):
> 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



--
Michał Łabędzki
___________________________________________________________________________
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