Re: gcc warnings

[Bruno H. <br...@cl...>]

Hi Sam,

> The same story with ignoring GCC warnings today - I don't understand the
> subject and I am leaving it to you

I will deal with these GCC warnings. But to keep the story short:

  1) It is better to start with all warnings and disable the warnings
     on case-by-case basis, than to start with no warnings and enable them
     selectively. Reason: GCC keeps adding new, useful warnings for a number
     of years already. [1]

  2) clang has become a compiler to care about as well, and clang has also
     a number of useful (and a small number of not useful) warnings.

Bruno

[1] https://www.gnu.org/software/gnulib/manual/html_node/manywarnings.html