Difference between revisions of "Code Cleanup"

From BRL-CAD
(coverity section)
(link in the images and site)
Line 6: Line 6:
 
=Coverity Scan=
 
=Coverity Scan=
  
Since 2006, BRL-CAD has been a participant in the Coverity Scan Initiative, an effort funded by the U.S. Department of Homeland Security to improve the quality, safety and security of open source software.  Coverity performs a static source code analysis (one of the best) and generates a detailed report of issues detected.
+
[[Image:CoverityExample3.png|right|256px|... showing pretty awesome detection of a potentially uninitialized variable use]]
 +
 
 +
Since 2006, BRL-CAD has been a participant in the [http://scan.coverity.com/ Coverity Scan Initiative], an effort funded by the U.S. Department of Homeland Security to improve the quality, safety and [http://en.wikipedia.org/wiki/Open_source_software_security security] of open source software.  Coverity performs a static source code analysis (one of the best) and generates a detailed report of issues detected.
  
 
The BRL-CAD scan was previously "stuck" but we're now back online and operational!  For an interesting preview of some of the kinds of things reported, here are some screenshots:
 
The BRL-CAD scan was previously "stuck" but we're now back online and operational!  For an interesting preview of some of the kinds of things reported, here are some screenshots:
  
... showing a potential (albeit unlikely) NULL dereference:
+
[[Image:CoverityExample1.png|left|256px|... showing a potential (albeit unlikely) NULL dereference]]
http://brlcad.org/tmp/cov1.png
 
  
... showing secure coding practice suggestions:
+
[[Image:CoverityExample2.png|none|256px|... showing secure coding practice suggestions]]
http://brlcad.org/tmp/cov2.png
 
  
... showing pretty awesome detection of a potentially uninitialized variable use:
 
http://brlcad.org/tmp/cov3.png
 
  
 
Those and many other issues are all managed through a private website that is only accessible if you have an account.  If you're going to help, fantastic.  Get in touch with a developer to have your account created.
 
Those and many other issues are all managed through a private website that is only accessible if you have an account.  If you're going to help, fantastic.  Get in touch with a developer to have your account created.

Revision as of 13:15, 11 April 2011

The BRL-CAD source code is large with a lot of history. In order to survive decades of development, considerable time and attention is put forth towards improving code maintainability and code quality. One of the best ways to get involved in BRL-CAD open source development is to help clean up source code.

Cleaning up the source code helps you become familiarized with BRL-CAD and improves maintainability. There are a variety of ways you can clean up source code, but some of our specific efforts in place to help refactor BRL-CAD are:


Coverity Scan

... showing pretty awesome detection of a potentially uninitialized variable use

Since 2006, BRL-CAD has been a participant in the Coverity Scan Initiative, an effort funded by the U.S. Department of Homeland Security to improve the quality, safety and security of open source software. Coverity performs a static source code analysis (one of the best) and generates a detailed report of issues detected.

The BRL-CAD scan was previously "stuck" but we're now back online and operational! For an interesting preview of some of the kinds of things reported, here are some screenshots:

... showing a potential (albeit unlikely) NULL dereference
... showing secure coding practice suggestions


Those and many other issues are all managed through a private website that is only accessible if you have an account. If you're going to help, fantastic. Get in touch with a developer to have your account created.

PLEASE don't bother inquiring if you're only interested in looking at results or poking around.

We'll probably have you fix an issue or two first to make sure you're serious.


The HACKING File

Our tried and true developer guidelines HACKING file identifies numerous stylistic concerns and source code conventions that the entire BRL-CAD source code should conform to. When in doubt, consult the dev guidelines.