As software developers, we know you always strive to become a more professional programmer. To do that, you need to use the right tools to support your code development efforts and improve your code quality. However, there are so many tools that it could be difficult to know what to choose, and it is technically challenging to set them up yourself. This makes you feel like you are not fulfilling your potential as a developer. We believe you don’t have to be a tech wizard to use such tools and that they should be easily accessible to all developers. We understand how frustrating it feels to try and find hidden bugs in your code. We know what it’s like to spend hours writing support documentation for your code when you’d rather spend your time actually writing code. That’s why our team of expert C/C++ developers created SoftaCheck.
Here’s how it works First, sign up for the app using your GitHub account. Second, choose the repository you want to analyze. And finally, after a few moments, review all the detected bugs and browse through your newly created support documentation. So, sign up now, so you can stop wasting your time releasing software programs with bugs and, instead, start writing high-quality code and become a professional software developer.
No features have been listed yet.
Based on our record, Cppcheck seems to be more popular. 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.
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 / 2 months 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: 11 months 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 1 year 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 1 year 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 1 year ago
CodeFactor.io - Automated Code Review for GitHub & BitBucket
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.
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
CodeSonar - CodeSonar, produced by GrammaTech, is source and binary code analysis software that finds critical defects that can crash systems, result in unexpected operations, threaten security, and more.