Wireshark-dev: Re: [Wireshark-dev] error in epan/tfs.h
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: sagar sg <sagu072@xxxxxxxxx>
Date: Mon, 18 Jul 2011 18:52:39 +0530
Okay, you mean to say we have to add the extern c { tfs.h } to the wireshark code ?

On Mon, Jul 18, 2011 at 6:45 PM, Andreas <AndreasSander1@xxxxxxx> wrote:
Am 18.07.2011 10:12, schrieb Guy Harris:


On Jul 18, 2011, at 1:02 AM, Helge Kruse wrote:

I use always C++ to write my custom dissectors. Did you surround the Wireshark #include with extern "C" like this?

Perhaps Wireshark should surround the body of epan/tfs.h with that....

Well, Wireshark is a C project. It uses C libraries as the GTK library. Therefore there is no need to add the 'extern "C"' guards to compile Wireshark.

It would be helpful, if all Wireshark header files add theses guards. This would improve the compatibility with C++ compilers. But this may be error prone, since the authors must remember this when creating a new header file. A missing guard would not be detected as long as a C++ user will use it. Therefore I prefer to set the guards in the consuming C++ project.



___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
           mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe