News for hackers. Stuff that matters.
Re:Rules for Developing Safety Critical Code [pdf] by raverbashing on Friday January 16, 2015 @08:18AM (#8898633)
Of course, this is not as simple as it seems.

1 - Some tools and libraries (like GTK - yeah) like to throw unfixable warnings. "Yeah, this platform is missing this feature so let's throw a warning"

2 - Sometimes fixing a warning results in something much more complicated than the original code. (see for example half of PyLint warnings)

So, for that to work it's important the tool warnings are good (and at least with GCC on C they usually are)

Re:Rules for Developing Safety Critical Code [pdf] by RogerL on Friday January 16, 2015 @09:48AM (#8899167)
When I did mission critical work we basically did not use libraries if at all possible. You need to know how everything works, and you need to be able to fix it. I'm pretty sure the NASA paper is written within that context.

But yes, that is a huge pet peeve of mine. I have all my QT header includes wrapped with pragmas to turn off warning because otherwise they spit out endless, useless warnings.

Re:Rules for Developing Safety Critical Code [pdf] by smackfu on Friday January 16, 2015 @09:48AM (#8899169)
3 - a compiler adds a new warning that triggers on existing code.

So when you go to do a minor fix, do you also touch other code that now triggers a warning?

Re:Rules for Developing Safety Critical Code [pdf] by raverbashing on Friday January 16, 2015 @09:58AM (#8899231)
True. Tell me about it.

Or worse, they break existing code (I've seen this happen with C++ on GCC)