Re: gcc warnings

[Sam S. <sd...@gn...>]

Hi Bruno,

My general attitude to compiler warnings is that each such warning is a bug.
Either it is a bug in the code being compiled, or it is a bug in the compiler.
Thus disabling a warning is merely closing one's eyes.
It can be a stop-gap (let's disable warning A while we are working on
warning B), but never permanent.
I know you disagree, and I doubt that I will convince you or vv.
Thanks for dealing with the issue.


> * Bruno Haible <oe...@py...t> [2017-03-13 09:47:49 +0100]:
>
> 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

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://camera.org
http://iris.org.il http://mideasttruth.com http://islamexposedonline.com
Stupidity, like virtue, is its own reward.