I would like to draw attention to the document: "The Power of 10: Rules for Developing Safety-Critical Code" from NASA/JPL Laboratory. https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code
They tells, for example: Rule 10: All code must be compiled, from the first day of development, with all compiler warnings enabled at the most pedantic setting available. All code must compile without warnings. All code must also be checked daily with at least one, but preferably more than one, strong static source code analyzer and should pass all analyses with zero warnings. You can see entire document here: https://web.eecs.umich.edu/~imarkov/10rules.pdf On 29.09.2017 19:28, Jens Alfke wrote: > >> On Sep 29, 2017, at 1:07 AM, Denis V. Razumovsky <t...@denis.im> wrote: >> >> Please remove multiple warnings from compiler about optimisation, >> variable conversion, signed overflow and many more potential errors. > This comes up a lot. SQLite is incredibly thoroughly tested* and > performance-tuned, but the developers have chosen not to use compiler > warnings to identify problems. It’s not the decision I’d have made > personally, but I can’t argue with the results. > > —Jens > > * http://www.sqlite.org/testing.html > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
