Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!stc!datlog!dlhpedg!cl
From: cl@datlog.co.uk (Charles Lambert)
Newsgroups: comp.software-eng
Subject: Re: C code metrics
Summary: Let's keep talking until we find something that works.
Keywords: metrics quality
Message-ID: <816@dlhpedg.co.uk>
Date: 6 Jul 88 08:22:00 GMT
References: <4820@cg-atla.UUCP>
Sender: news@dlhpedg.co.uk
Reply-To: cl@datlog.co.uk (Charles Lambert)
Distribution: comp
Organization: FSD@Data Logic Ltd, Queens House, Greenhill Way, Harrow, London.
Lines: 15

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
>summarize to the net.  Thanks in advance.

Can we keep this discussion in the open, please?  I know it gets hashed over
fairly regularly but it is important and perspectives are changing all the
time.  At the moment,  there are several initiatives in the UK to promote
better engineering practices in software;  we cannot engineer what we cannot
measure,  so any discussion of methods is useful.

Charlie