Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ssg0!petej
From: petej@ssg0.UUCP (Peter M. Jansson)
Newsgroups: comp.lang.c
Subject: Re: Determining C Complexity
Summary: What quantifiable experience do you have with metrics?
Keywords: C, complexity, metrics, cyclomatic complexity, McCabe
Message-ID: <204@ssg0.UUCP>
Date: 1 Aug 90 14:35:42 GMT
References: <2592@dataio.Data-IO.COM> <157@srchtec.UUCP> <7967@jarthur.Claremont.EDU> <2600@dataio.Data-IO.COM>
Reply-To: petej@ssg0.UUCP (Peter M. Jansson)
Distribution: na
Organization: Pharmacia Diagnostics, Columbia, MD
Lines: 14

In article <2600@dataio.Data-IO.COM> bright@Data-IO.COM (Walter Bright) writes:
>I'm arguing against using metrics at all. If you're limited in resource,
>decide to review the newest code, or the most critical.
>

Has anyone really run a study of how code metrics correlate to
maintenance costs?  Something like "In this module, the complexity was
high, and we had to make more changes to it after delivery" for a
reasonable size system would be helpful.

Data like these would help to determine in what circumstances metrics
are useful.

By the way, how does one define "most critical?"