From 6e3f2d3f3ce9ca4d7d8155bf3ce188d0ee3e895c Mon Sep 17 00:00:00 2001 From: Jason Turner Date: Thu, 5 Jan 2017 23:05:18 -0700 Subject: [PATCH] Add note on containing warning disabling code. --- 02-Use_the_Tools_Available.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/02-Use_the_Tools_Available.md b/02-Use_the_Tools_Available.md index c0dccf6..22c5928 100644 --- a/02-Use_the_Tools_Available.md +++ b/02-Use_the_Tools_Available.md @@ -244,6 +244,8 @@ Both of these tools use coverage reporting to find new code execution paths and If it is determined by team consensus that the compiler or analyzer is warning on something that is either incorrect or unavoidable, the team will disable the specific error to as localized part of the code as possible. +Be sure to reenable the warning after disabling it for a section of code. You do not want your disabled warnings to [leak into other code](http://www.forwardscattering.org/post/48). + ## Testing CMake, mentioned above, has a built in framework for executing tests. Make sure whatever build system you use has a way to execute tests built in.