Re: [Wireshark-dev] Are we fully moved over to C++ compilers?

2023-05-17 Thread Pascal Quantin
Hi Gilbert,

17 mai 2023 23:41:21 Gilbert Ramirez :

> What's the state of our toolchain requirements for wireshark and all the 
> programs within it?
> The CMakeLists.txt indicates we need C++ 11, but also has variables for 
> C_ONLY_FLAGS
>
> Some .c/.h files have "#ifdef __cplusplus" and others don't.
>
> Basically, if I'm working on a new feature in common code for tshark and 
> wireshark, can I rely on C++ and the STL, or must I restrain myself to C and 
> glib?

You should stick to C (C++ being used for Qt code). Lately we allowed the use 
of stdint.h types if I'm not mistaken, but 99.9% of the code still uses glib 
types and functions.

Best regards,
Pascal.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


[Wireshark-dev] Are we fully moved over to C++ compilers?

2023-05-17 Thread Gilbert Ramirez
What's the state of our toolchain requirements for wireshark and all the
programs within it?
The CMakeLists.txt indicates we need C++ 11, but also has variables for
C_ONLY_FLAGS

Some .c/.h files have "#ifdef __cplusplus" and others don't.

Basically, if I'm working on a new feature in common code for tshark and
wireshark, can I rely on C++ and the STL, or must I restrain myself to C
and glib?

Thanks,

Gilbert
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe