CodePeer
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "CodePeer" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|CodePeer|concern=No evidence of notability as established by significant coverage in multiple, independent reliable sources.}} ~~~~ Timestamp: 20140611095105 09:51, 11 June 2014 (UTC) Administrators: delete |
CodePeer is an open source static analysis tool, which identifies constructs that are likely to lead to run-time errors such as buffer overflows, and it flags legal but suspect code, typical of logic errors [1] in Ada programs. CodePeer also produces a detailed analysis of each subprogram, including pre- and post-conditions, making it easier to find potential bugs and vulnerabilities early.[2]
CodePeer is produced by AdaCore, a computer software company with North American headquarters in New York and European headquarters in Paris.
See also
- Static code analysis
- Software testing
- Software Security Assurance
- List of tools for static code analysis
References
- ^ Cole, Bernard. "AdaCore releases new CodePeer static analysis tool". Embedded. Retrieved 17 June 2014.
- ^ Walsh, Trudy. "CodePeer spots Ada code errors early". GCN. Retrieved 17 June 2014.
External links
- AdaCore web site
- AdaCore's CodePeer developed in partnership with SofCheck
- Why is static analysis a challenge? - interview with Michael Friess
- Tucker Taft, "Advanced static analysis meets contract-based programming", 2013.
- Embedded Computing Design, "Making static analysis a part of code review", 2009.