rlandsma@bbn.com (Rick Landsman) (03/22/91)
Archive-name: case/metric/metrics/1991-03-21
Archive: uunet.uu.net:/comp.sources.unix/volume20/metrics [137.39.1.2]
Original-posting-by: rlandsma@bbn.com (Rick Landsman)
Original-subject: Re: WANTED: "C" code line counter program
Reposted-by: emv@msen.com (Edward Vielmetti, MSEN)
Sorry if this has already been mentioned.
We have been using a "C" SLOC counting tool available via anonymous
FTP from uunet.uu.net comp.sources.unix archives. I believe it is
available in volume20,21 or 22 but interested parties should get the
Index and search it for "metrics" to see where the actual package is
located in the archive.
Not only does it generate slocs (we modified it to count ASSY lines as
well), it generates McCabe and Halstead complexity metrics for C
modules. We have found it very useful.
regards rick landsman - bbn
Rick Landsman
address: uunet.uu.net!bbn.com!rlandsman
rlandsman@bbn.comrlandsma@bbn.com (Rick Landsman) (04/06/91)
Archive-name: case/metric/metrics/1991-04-04
Archive-directory: uunet.uu.net:/comp.sources.unix/volume20/metrics/ [192.48.96.2]
Original-posting-by: rlandsma@bbn.com (Rick Landsman)
Original-subject: Re: WANTED: "C" code line counter program
Reposted-by: emv@msen.com (Edward Vielmetti, MSEN)
I have mentioned this before but for those that missed it, there is a
"C" package called metrics in volume 20 of the comp.sources.unix
archive available via anonymous ftp from uunet.uu.net that generates
both McCabe and Halstead metrics from "C" files. We have found it
useful as a way to determine POTENTIAL software functions for
re-design to reduce ERROR PRONENESS :-) due to overly complex control
and syntactical complexity. This is one of the tools we use for defect
reduction by targetting error prone modules.
There is documentation included with the package that discusses some
of the Halstead volume and other metrics used by the author.
Rick Landsman
address: uunet.uu.net!bbn.com!rlandsman
OR
rlandsman@bbn.com