ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Idle Thought - Compiling with C++

From: Evan Huus <eapache@xxxxxxxxx>
Date: Tue, 12 Feb 2013 18:20:34 -0500
On Tue, Feb 12, 2013 at 5:00 PM, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
> On 02/12/2013 10:53 PM, Gerald Combs wrote:
>> On 2/12/13 1:17 PM, Jaap Keuter wrote:
>>> On 02/11/2013 06:36 PM, Evan Huus wrote:
>>>> Moving just to a C++ compiler shouldn't cause problems for anybody.
>>>> While C++ isn't technically a superset of C, it is trivial for C
>>>> programmers to avoid the few areas of incompatibility (as far as I
>>>> know there are simply a few more reserved words like 'new' to avoid in
>>>> variable names).
>>>>
>>>
>>> Add this the the reading list: http://david.tribble.com/text/cdiffs.htm
>>> May not be all applicable (C89 and such) but show what a can-o-worms it can be.
>>> That's probably where that 7k number comes from.
>>
>> When starting on the Qt code I found the Google C++ Style Guide to be
>> helpful: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
>> Anyone outside of Google probably shouldn't adhere to it strictly but
>> it provides clean, concise descriptions on why they do and don't do
>> various things.
>>
>> We should steal the format for README.developer, BTW.
>
> Interesting read, although...
>
> "We do not use C++ exceptions."
>
> This is somewhat of a bummer.

I think their reasoning is fairly sound on this point, but doesn't
really apply to the way we already use exceptions. Converting our
existing exceptions to C++ equivalents would be a definite win, since
we've already got the mechanisms in place to handle them safely.