fish-shell/.cppcheck.suppressions

// suppress all instances of varFuncNullUB: "Passing NULL after the last typed
// argument to a variadic function leads to undefined behaviour." That's
// because all the places we do this are valid and won't cause problems even
// on a ILP64 platform because we're careful about using NULL rather than 0.
varFuncNullUB
// Suppress the warning about unmatched suppressions. At the moment these
// warnings are emitted even when removing the suppression comment results in
// the warning being suppressed. In other words this unmatchedSuppression
// warnings are false positives.
unmatchedSuppression

memleak:src/env_universal_common.cpp
flockSemanticsWarning:src/env_universal_common.cpp
flockSemanticsWarning:src/history.cpp
improve linting tool I found that after fixing the args to `cppcheck` it started reporting lots of varFuncNullUB warnings. Suppress them as they should be safe to ignore. Also, improve the readability of the script. 2016-11-15 03:20:12 +00:00			`// suppress all instances of varFuncNullUB: "Passing NULL after the last typed`
			`// argument to a variadic function leads to undefined behaviour." That's`
			`// because all the places we do this are valid and won't cause problems even`
			`// on a ILP64 platform because we're careful about using NULL rather than 0.`
			`varFuncNullUB`
fix some lint warnings This fixes some of the IWYU and cppcheck lint warnings. And only on macOS (formerly OS X). Fixing these types of warnings on a broader set of platforms should be done but this is a baby step to making `make lint-all` have few, if any, warnings. This reduces the number of lines in the `make lint-all` output on macOS by over 500 lines. 2016-11-15 05:31:51 +00:00			`// Suppress the warning about unmatched suppressions. At the moment these`
			`// warnings are emitted even when removing the suppression comment results in`
			`// the warning being suppressed. In other words this unmatchedSuppression`
			`// warnings are false positives.`
			`unmatchedSuppression`
check if locking takes too long If acquiring a lock on the history or uvar file takes more than 250 ms disable locking of the file. On systems with broken remote file system locking it can cause tens of seconds delay after running each command which can make the shell borderline unusable. This also changes history file locking to use flock() rather than fcntl() to be consistent with uvar file locking. It also implements the 250 ms time limit before giving up on locking. Fixes #685 2016-12-16 05:50:27 +00:00
			`memleak:src/env_universal_common.cpp`
			`flockSemanticsWarning:src/env_universal_common.cpp`
			`flockSemanticsWarning:src/history.cpp`