Hi saifi

Thanks for the response,

Tim Littlefair's CCCC tool does solve my purpose, but after studying splint
over a week, my expections about static analysis tool is increased that, if
I can get a mix of splint results and CCCC(branch coverage), it will be best
tool. This mix gives lot of options but as in splint can enable it and
disable it.
Have you come across of such tool, like RSM-
http://msquaredtechnologies.com/ , is quite good mix of project matrix
generation and static analysis, but  its not  open source tool.

Thanks in advance
_Bhagwat.


On Mon, Mar 3, 2008 at 12:26 PM, Saifi Khan <[EMAIL PROTECTED]>
wrote:

>   On Mon, 3 Mar 2008, Bhagwat Masalkar wrote:
>
> > Date: Mon, 3 Mar 2008 10:08:44 +0530
> > From: Bhagwat Masalkar <[EMAIL PROTECTED]<bhagwat.masalkar%40gmail.com>
> >
> > Reply-To: <[email protected] <twincling%40yahoogroups.com>>
> > To: <[email protected] <twincling%40yahoogroups.com>>
> > Subject: [twincling] Looking for open source static code analysis tool
>
> >
> > Dear all
> >
> > This is my first post to this community, I am looking for a open source
> tool
> > for static analysis. We mainly work on C language, C++ is not mandatory.
> > I got Splint from tool, I had downloaded it and working on from last one
> > week, I was not able to locate some points in this tool, which
> commercial
> > tools provide
> > ie
> > using Splint how to check the cyclometric complexity or Macabe's
> > complexity .
> > Also does not provide for how comment density in code ie no count for
> > minimum code comment availability.
> >
> > please suggest some tool .
> >
> > thanks
> > bhagwat.
> >
>
> Hi Bhagwat:
>
> First of all a very warm welcome. Hope you have a good time here.
>
> Tools like Splint or CQUAL are type-based analysis tools.
>
> Cyclometric complexity or more correctly 'conditional complexity'
> of the source code is calculated by creating a graph of the source,
> wherein each statement is a node. The arrows between the nodes are
> potential execution routes.
>
> Thus the tool needs to ascertain:
> 1. branch coverage
> 2. path coverage
>
> while gcov does coverage analysis, it does not calculate conditional
> complexity.
>
> Tim Littlefair started an Open Source project as part of his MS project.
>
> You can see it here http://cccc.sourceforge.net/
> It works both on Linux and MS operating systems.
>
> Tim's MS and PhD thesis is available at
> http://www.chs.ecu.edu.au/~tlittlef/index.html<http://www.chs.ecu.edu.au/%7Etlittlef/index.html>
>
> Perhaps this can get you started in the right direction.
>
> thanks
> Saifi.
>  
>

Reply via email to