Re: [Wireshark-dev] Hierarchy of fields & offsets again, more potential offenders

On Wed, Aug 9, 2017 at 7:05 PM, Pascal Quantin wrote: > Hi Stig (and Sake), > > 2017-08-02 22:24 GMT+02:00 Stig Bjørlykke : > >> On Wed, Aug 2, 2017 at 10:03 PM, Sultan, Hassan via Wireshark-dev >> wrote: >> > Regarding

Re: [Wireshark-dev] Using C++ for a test tool linking to wireshark

On Aug 9, 2017, at 12:01 PM, Sultan, Hassan wrote: > Awesome :) so no concerns about C++ 11 then ? There's "concerns about C++" and there's "concerns about C++ 11". The Wireshark Developer's Guide:

Re: [Wireshark-dev] "[UNVERIFIED SENDER]Re: Using C++ for a test tool linking to wireshark

Awesome :) so no concerns about C++ 11 then ? > -Original Message- > From: Guy Harris [mailto:g...@alum.mit.edu] > Sent: Wednesday, August 09, 2017 11:55 AM > To: Developer support list for Wireshark > Cc: Sultan, Hassan > Subject:

Re: [Wireshark-dev] Using C++ for a test tool linking to wireshark

On Aug 9, 2017, at 11:48 AM, Sultan, Hassan via Wireshark-dev wrote: > I’ve noticed everything in Wireshark seems to be in C89 ...except for the files in ui/qt and subdirectories thereof, and wireshark-qt.cpp in the top-level directory.

[Wireshark-dev] Using C++ for a test tool linking to wireshark

Hi, I've noticed everything in Wireshark seems to be in C89 , which I guess is understandable for portability reasons. I'm curious whether you guys would be okay with having an external test tool be in C++ 11 though (think of something like tshark or rawshark but much smaller/simpler and for

Re: [Wireshark-dev] Hierarchy of fields & offsets again, more potential offenders

Hi Stig (and Sake), 2017-08-02 22:24 GMT+02:00 Stig Bjørlykke : > On Wed, Aug 2, 2017 at 10:03 PM, Sultan, Hassan via Wireshark-dev > wrote: > > Regarding tcp.payload, I don't think tcp.payload in itself has any > problems. I think the issue lies