Jump to content

Talk:List of tools for static code analysis

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Barry abs (talk | contribs) at 21:22, 10 January 2007. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

I've rendered the C# tool in a table format as an example. The columns chosen aren't definitive, if you can think of more relevant ones then please add them. If/when we get it 'right' we could do the same for the other language tools. Have a look at the tables on this page to see where we could go with it.--Hooperbloob 02:41, 15 June 2006 (UTC)[reply]

Valgrind

valgrind doesn't provide static analysis, does it? You have to actually run the executable. Then it should be removed. --Nephtes 18:09, 28 August 2006 (UTC)[reply]

Categorization

This entry could use a sub-categorization concerning the cost/license of the various individual solutions, so that people can easily check for tools that match their financial/license requirements

VB

Several tools in the Visual Basic category don't seem to support Visual Basic, but C# or C++.

C++

Shouldn't [Oink] be included, being all popular an' that? barry_abs 21:22, 10 January 2007 (UTC) 21:20, 10 January 2007 (UTC)