DocFX
Doxygen
Daux.io
Docsify.js
Natural Docs
Outline Wiki
NDoc
Docpress
Cppcheck
Clang Static Analyzer
Coverity Scan
lgtm.com
SonarQube
VisualCodeGrepper
Flawfinder
Parasoft C/C++test
DocFX CppcheckCppcheck is recommended for C/C++ developers and development teams, particularly those responsible for maintaining large codebases or projects where code quality and reliability are paramount. It is also beneficial for educational purposes, where students and new developers can learn about potential pitfalls in C/C++ programming.
Cppcheck might be a bit more popular than DocFX. We know about 10 links to it since March 2021 and only 8 links to DocFX. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Documentation that falls out of sync with your API is worse than no documentation at all. Tools like DocFX, Sandcastle, and Doxygen process XML documentation files automatically generated by the .NET compiler from your source comments. - Source: dev.to / 11 months ago
This is a better looking version of what Java and C# have had for a long time (kudos to the author for that!), is that the inspiration for this tool? https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javadoc.html https://dotnet.github.io/docfx/ I saw the author mentioned in another comment that they found themselves peeping inside type declaration files "too often". While I do often use sites generated... - Source: Hacker News / over 2 years ago
Actually, we use it for OptiTune, it's called "docfx" https://dotnet.github.io/docfx/. Source: over 4 years ago
We would really prefer to use a somewhat generic pre-made tool for this (such as DocFX) compared to rolling our own solution. We can roll our own solution... But would prefer not to so that we can minimize development and maintenance overhead. Source: over 4 years ago
I use docfx from microsoft to generate documentation for all my oss libraries. Source: over 4 years ago
I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / over 2 years ago
Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: about 3 years ago
For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: over 3 years ago
Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: over 3 years ago
Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 3 years ago
Doxygen - Generate documentation from source code
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
Daux.io - Daux.io is a documentation generator that uses a simple folder structure and Markdown files to...
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Docsify.js - A magical documentation site generator.
lgtm.com - lgtm.com is a platform for code analytics.
