I like warnings, I like to turn them all on, and I like to use --enable-gcc-warnings to force them on my attention.
And then just occasionally the warnings are misguided. One example is old APIs. For example, from terminfo: char *tigetstr (char *capname); So, one can't call, e.g. tigetstr("kbs") without getting a warning. But this is clearly nuts: there's no way tigetstr is going to overwrite its argument. So, what's a hacker to do? I could turn off cast warnings globally, but that would lose me lots of good warnings. I don't even really want to turn it off for an entire source file. Other ideas? -- http://rrt.sc3d.org