3 ms·
And how exactly could SQLite benefit from warning-free compilation? It not only appears to work but it does its job pretty well. Unit tests prove a different l
by pestaa 15y ago
And how exactly could SQLite benefit from warning-free compilation? It not only appears to work but it does its job pretty well.
Unit tests prove a different level of semantics that these warnings cannot substitute (although possibly complement).
- palish 15y agoTests and warnings compliment each other nicely. "My, you're looking testy today!" ... burgerbrain points out something very important: Code bases with warnings tend to be degenerate. Tend to. SQLite is not one of them. But I've seen several large codebases. The two which were beautiful also had zero warnings, and the ~dozen others ranged from "meh" all the way down to "lol, grab a snickers". This is obviously not enough data to draw any meaningful statistical conclusions from --- but it would be silly to ignore it completely. Good C/C++ programmers tend to respect compiler warnings.
- awj 15y ago> Unit tests prove a different level of semantics that these warnings cannot substitute (although possibly complement). That, actually, is part of the point. Unit tests check for correct expression of the problem domain (and solution). Compiler warnings check for correct expression of language constructs. It's possible, though not usually likely, for incorrect language usage to mask incorrect implementations.