On 10/25/2016 06:38 PM, Dominik Vogt wrote:
Right. A solution must disable the warnings on any compilers and
versions the developers use, and not break compilation anywhere.
The way I generally do it is check for the compiler, and then define a
macro for gcc and for clang using those
On 10/22/2016 07:35 PM, Dominik Vogt wrote:
And the least invasive way to prevent this is faking a read with
the coid-cast.
I assume marking the variable as potentially unused via
__attribute__((unused)) or similar is undesirable because it depends on
compiler-specific extensions? Then
