AppRefactoring
Codegrip
SonarQube
TSLint
Reek
Source Insight
CodeClimate
codebeat
Cppcheck
SonarQube
Clang Static Analyzer
Coverity Scan
Parasoft C/C++test
PVS-Studio
Polyspace
lgtm.com
AppRefactoring service for developers and companies that release many applications. Using popular programming languages and convenient file formats, the system analyzes your code in just a few clicks. In addition, you can compare the code with the personal/team database and see their intersections.
AppRefactoring CppcheckNo features have been listed yet.
Cppcheck 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.
Based on our record, Cppcheck should be more popular than AppRefactoring. It has been mentiond 10 times since March 2021. 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.
Carrying out your legacy code refactoring exercise manually, takes a lot of time and resources. It is therefore best to make use of an automated tool like AppRefactoring. AppRefactoring is a tool that helps with identifying intersections and duplicates in project codes and thus provides recommendations for refactoring. It is available for several programming languages such as Java, Swift, Javascript, Typescript,... - Source: dev.to / over 2 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 1 year 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 2 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: about 2 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: about 2 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 2 years ago
Codegrip - Codegrip is an automated code review tool that not only provides the user with detailed code review reports but also gives suggested solutions to solve the issues. It is the only automated code review platform that does not store the user's code
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
TSLint - An extensible static analysis linter for the TypeScript language
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Reek - Code smell detector for Ruby