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:21:57 -0500
On Tue, Feb 12, 2013 at 4:53 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> 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.

Rather tangentially, I would like to split README.developer into two:
- README.developer (for style and general practices)
- README.dissector (for all the stuff specific to writing a dissector)

Its current form is growing rather long and hard to navigate.