Re: [Wireshark-dev] Do we still need/want -Wc++-compat?

GTK build breaks for 3.18 with Werror=c++-compat ('and' is a reserved C++ keyword). It should arguably be fixed upstream, I patched my GTK installation, but can this warning be removed? On 10/09/2015 06:47 PM, Evan Huus wrote: On Fri, Oct 9, 2015 at 1:40 PM, Guy Harris

Re: [Wireshark-dev] Do we still need/want -Wc++-compat?

On Sep 30, 2015, at 9:59 PM, Evan Huus wrote: > On Thu, Oct 1, 2015 at 12:38 AM, Guy Harris wrote: >> >> On Sep 30, 2015, at 6:53 PM, Guy Harris wrote: >> >>> I think the intent was to be able to run Wireshark's C code through C++

Re: [Wireshark-dev] Do we still need/want -Wc++-compat?

On Fri, Oct 9, 2015 at 1:40 PM, Guy Harris wrote: > > On Sep 30, 2015, at 9:59 PM, Evan Huus wrote: > >> On Thu, Oct 1, 2015 at 12:38 AM, Guy Harris wrote: >>> >>> On Sep 30, 2015, at 6:53 PM, Guy Harris wrote: >>>

Re: [Wireshark-dev] Do we still need/want -Wc++-compat?

On Thu, Oct 1, 2015 at 12:38 AM, Guy Harris wrote: > > On Sep 30, 2015, at 6:53 PM, Guy Harris wrote: > >> I think the intent was to be able to run Wireshark's C code through C++ >> compilers; I can't find the mail where this was discussed, but, as I >>

[Wireshark-dev] Do we still need/want -Wc++-compat?

I think the intent was to be able to run Wireshark's C code through C++ compilers; I can't find the mail where this was discussed, but, as I remember, the issue was that Microsoft were dragging their feet on C99 support, and we wanted to be able to use at least some features present in both C99

Re: [Wireshark-dev] Do we still need/want -Wc++-compat?

On Sep 30, 2015, at 6:53 PM, Guy Harris wrote: > I think the intent was to be able to run Wireshark's C code through C++ > compilers; I can't find the mail where this was discussed, but, as I > remember, the issue was that Microsoft were dragging their feet on C99 >