Update 02-Use_the_Tools_Available.md

This commit is contained in:
Jason Turner
2018-04-27 19:28:12 -06:00
committed by GitHub
parent 2764eb398d
commit c58e6d75e6

View File

@@ -280,6 +280,10 @@ Both of these tools use coverage reporting to find new code execution paths and
MSVC's [Control Flow Guard](https://msdn.microsoft.com/en-us/library/windows/desktop/mt637065%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396) adds high performance runtime security checks.
### Checked STL Implementations
* `_GLIBCXX_DEBUG` with GCC's implementation libstdc++ implementation. See [Krister's blog article](https://kristerw.blogspot.se/2018/03/detecting-incorrect-c-stl-usage.html).
## Ignoring Warnings
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.
@@ -316,6 +320,10 @@ Don't forget to make sure that your error handling is being tested and works pro
## Other Tools
### Lizard
[Lizard](http://www.lizard.ws/) provides a very simple interface for running complexity analysis against a C++ codebase.
### Metrix++
[Metrix++](http://metrixplusplus.sourceforge.net/) can identify and report on the most complex sections of your code. Reducing complex code helps you and the compiler understand it better and optimize it better.