No description
fd74aa0720
This change allows the maximum issues to be passed in as an argument. If nothing is passed, then the existing build-in maximum is used. Retaining the existing built-in value makes sense for home users to keep track of their local build (otherwise they would have to remember the prior number of warnings and pass that value in for subsequent builds). Motivation: until now the built-in maximum covers the build permutation that happens to generate the most warnings versus other builds. In some cases new warnings may not be cause if they elicit a warning from the lesser-warning build(s) or compilers, but not in the maximum-warning build. This change lets us tighten-down the warning uniquely for each build, so we can be sure all new warnings are flagged to the developer. |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| include | ||
| scripts | ||
| src | ||
| visualc_net | ||
| .gitignore | ||
| .pylint | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| README.md | ||
| THANKS | ||
| VERSION | ||