Re: gcc warnings
Bruno Haible <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <3226110.aSiTFGRRmn@omega> |
Hi Sam, > 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. No. Different projects need to enable different sets of warnings. That's why the warnings have names, so that we can selectively enable or selectively disable them. Look again at these examples: nw="$nw -Wsystem-headers" # Don't let system headers trigger warnings nw="$nw -Wundef" # All compiler preprocessors support #if UNDEF nw="$nw -Wtraditional" # All compilers nowadays support ANSI C Bruno ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel