Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!umix!b-tech!umich!neti1!bdr
From: bdr@neti1.uucp (Brian Renaud)
Newsgroups: comp.software-eng
Subject: Re: C code metrics
Summary: I have some C code metric analyzers
Keywords: metrics quality
Message-ID: <160@neti1.uucp>
Date: 13 Jul 88 15:45:34 GMT
References: <4820@cg-atla.UUCP> <816@dlhpedg.co.uk>
Distribution: comp
Organization: NETI, Inc.
Lines: 36



In article <816@dlhpedg.co.uk>, cl@datlog.co.uk (Charles Lambert) writes:
> In article <4820@cg-atla.UUCP> bradlee@cg-atla.UUCP (Rob Bradlee X5153) writes:
> >Request for Help:
> >
> >I'm looking both for information explaining how to judge the size and
> >quality of C code, and also for any tools that will automatically
> >perform some analysis.  Send me email, and if I get any good info I'll

I have some programs (shell/awk/C, etc.) which provide some metrics
for C programs.   As I remember, they consist of:

   line counter - print actual lines of code (useful for COCOMO modeling)
                  as well as blank lines, number of comments, comment lines

   halstead     - provide various software science metrics, based on Halstead's
                  work

   mccabe       - program complexity analyzer, based on McCabe, etc.

I also have some rather arcane scripts which will run these tools on
a specified set of programs and produce some flat files containing only
the metrics I have found to be statistically significant.  (You may find
that these metrics are not right for you, I only analyzed two 30K DSI
projects.)

If you would like these let me know.  Email is the best way to reach me,
since my access to this news feed is rather shaky.

Brian
--
Brian Renaud	bdr%huron.uucp@umix.cc.umich.edu
		umix!huron!bdr
-- 
Brian Renaud      bdr%huron.uucp@umix.cc.umich.edu
Huron Systems     {umix,neti2}!huron!bdr