-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverity scan #333
Comments
I had used an analysis tool here: http://git.oschina.net/neohermit/dao/code_analysis, but it revealed nothing! Coverity could be (much) better, but I really don't like to sign up a new account just for a free trial. And generally I am not interested in using non free and non open source tools for the development of Dao. Not that I am against those tools, but that I simply don't want to become dependent on something that might become unavailable someday. |
Of course, you are welcome to try it on Dao. |
I share your opinion. The reason why I proposed it was to make Dao more "trustworthy" from the business point of view (i.e. checked by a well-known service). I'm considering trying it on Dao (I myself haven't tried Coverity scan yet, so it'll be a premiere ;)) at some point. |
As Dao is getting mature, we should probably run a bit more fine-grained static analysis than the clang one. There is a high-quality Coverity scan used by many projects (e.g. Red Hat uses it for all parts of their system) and is completely free for open-source projects.
The text was updated successfully, but these errors were encountered: