Explore >> Select a destination
|
You are here 
|
btorpey.github.io | ||
| | | | |
hackingcpp.com
|
|
| | | | | Basic techniques and tools for ensuring correctness: compiler warnings (gcc/clang/MSVC), assertions (assert/static_assert) and testing (with some doctest examples). | |
| | | | |
ddanilov.me
|
|
| | | | | Tips on how to make your compiler strictly follow the C++ standard | |
| | | | |
nrk.neocities.org
|
|
| | | | | [AI summary] This article provides an introduction to static analyzers for C, focusing on tools like compiler warnings, Cppcheck, GCC's fanalyzer, and clang-tidy, emphasizing ease of use, minimal setup, and reducing false positives. | |
| | | | |
kristerw.blogspot.com
|
|
| | | Pointers in the C language are more abstract than pointers in the hardware, and the compiler may surprise developers that think that pointe... | ||
