Even the quickest builds aren't worth much if your code has bugs. There are dozens of flags to warn you of potential issues in your code. This section will try to answer which ones you should consider enabling.
First, let's start with a slightly different matter: how not to get warned about issues with code from other libraries. Getting warned about issues that you can't really fix isn't useful. Fortunately, there are compiler switches to disable such warnings. In GCC, for instance, you have two types of include files: regular (passed using -I) and system ones (passed using -isystem). If you specify a directory using the latter, you won't get warnings from the headers it contains. MSVC has an equivalent for -isystem: /external:I. Additionally, it has other flags to handle external includes, such as /external:anglebrackets, which tells the compiler to treat all files included using angle brackets as external ones, thus disabling...
