.. -*- coding: utf-8; -*-

================
 Code analysis.
================
.. contemts::

About.
======

 * http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis

Splint.
=======

Secure Programming Lint, is a programming tool for statically checking C
programs for security vulnerabilities and coding mistakes. Formerly called
LCLint, it is a modern version of the Unix lint tool.

  http://en.wikipedia.org/wiki/Splint_%28programming_tool%29

Sparse.
=======

Sparse is a tool designed to find possible coding faults in the Linux kernel.

  http://en.wikipedia.org/wiki/Sparse
                Wikipedia page.

PMD.
====

PMD is a static ruleset based Java source code analyzer that identifies
potential problems.

PMD has plugins for JDeveloper, Eclipse, JEdit, JBuilder, Omnicore's CodeGuide,
NetBeans/Sun Studio, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, Hudson,
Jenkins, Sonar and Emacs.

  http://pmd.sf.net/
                Home page.
  http://en.wikipedia.org/wiki/PMD_%28software%29
                Wikipedia page.

Checkstyle.
===========

Static code analysis tool used in software development for checking if Java
source code complies with coding rules.

  http://en.wikipedia.org/wiki/Checkstyle
                Wikipedia page.

FindBugs.
=========

  http://en.wikipedia.org/wiki/FindBugs
                Wikipedia page.

Yasca.
======

Yasca leverages external open source programs, such as FindBugs, PMD, JLint,
JavaScript Lint, PHPLint, Cppcheck, ClamAV, Pixy, and RATS to scan specific file
types, and also contains many custom scanners developed for Yasca.

  http://yasca.org/
                Home page.
  http://yasca.org/
                Development home page.
  http://en.wikipedia.org/wiki/Yasca
                Wikipedia page.

Sonar.
======

Sonar uses various static code analysis tools such as Checkstyle, PMD, FindBugs,
Clover to extract software metrics.

  http://en.wikipedia.org/wiki/Sonar_%28software_quality%29
                Wikipedia page.