←back to thread

In Defense of C++

(dayvster.com)
185 points todsacerdoti | 2 comments | 16 Sep 25 19:40 UTC | HN request time: 0s | source
Show context
franky47 ◴[16 Sep 25 21:12 UTC] No.45268116[source]▶
What’s a good (ie: opinionated) code formatter and unit test framework for C++ these days?

I just had a PR on an old C++ project, and spending 8 years in the web ecosystem have raised the bar around tooling expectations.

Rust is particularly sweet to work with in that regard.

replies(3): >>45268262 #>>45268281 #>>45268294 #
lang4d ◴[16 Sep 25 21:25 UTC] No.45268281[source]▶
My go to for formatting would be clang-format, and for testing gtest. For more extensive formatting (that involves the compiler) clang-tidy goes a long way
replies(1): >>45270932 #
1. CalChris ◴[17 Sep 25 02:33 UTC] No.45270932[source]▶
I think you meant for more extensive static analysis. Clang-tidy is really awesome. There is also Facebook's Infer.

  https://fbinfer.com
replies(1): >>45275419 #
2. account42 ◴[17 Sep 25 13:10 UTC] No.45275419[source]▶
Clang tidy does both: it can run clang's analyzer [0] (also available with clang++ --analyze or the scan-build wrapper script which provides nicer HTML-based output for complex problems found), has it's own lightweight code analysis checks but also has checks that are more about formatting and ensuring idiomatic code than it is about typical static analysis.

MVSC [1] and GCC [2] also have built-in static analyzers available via cl /analyze or g++ -fanalyzer these days.

There is also cppcheck [3], include-what-you-use [4] and a whole bunch more.

If you can, run all of them on your code.

[0] https://clang-analyzer.llvm.org/

[1] https://learn.microsoft.com/en-us/cpp/build/reference/analyz...

[2] https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.h...

[3] https://cppcheck.sourceforge.io/

[4] https://github.com/include-what-you-use/include-what-you-use