Path: utzoo!attcan!uunet!ginosko!xanth!ames!mailrus!sharkey!mcf!mibte!gamma!towernet!pyuxp!nvuxj!nvuxr!jgn
From: jgn@nvuxr.UUCP (Joe Niederberger)
Newsgroups: comp.software-eng
Subject: Re: C source lines in file
Keywords: C
Message-ID: <1230@nvuxr.UUCP>
Date: 18 Aug 89 14:03:29 GMT
References: <35120@ccicpg.UUCP> <10707@smoke.BRL.MIL> <6500@pdn.paradyne.com>
Reply-To: jgn@nvuxr.UUCP (22143-Joe Niederberger)
Organization: Bell Communications Research
Lines: 28

In article <6500@pdn.paradyne.com> reggie@dinsdale.paradyne.com (George W. Leach) writes:
>In article <10707@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>>In article <35120@ccicpg.UUCP> swonk@ccicpg.UUCP (Glen Swonk) writes:
>>-Does anyone have a program or a method of determing
>>-the number of C source lines in a source file?
>>-My assumption is that comments don't count as source
>>-lines unless the comment is on a line with code.
>
>>What precisely is this supposed to measure?
>
>   I also want to know just what you are going to measure with this number?

I'm often surprised at these sorts of statements. He obviously wants to
(precisely) measure the number of C source lines in a source file,
disregarding lines that only contains comments (or blank lines also I
presume.) It seemed perfectly obvious to me 8^).

I suppose the question on some peoples minds is really "what are you
going to do with this measurement?" Perhaps he wants to look for a
correlation with some other measurements. Now, there's not much chance of
doing that if he can't obtain this measurement in the first place, is
there ? 

If these observations seem obvious, then just maybe they are correct.

This wasn't a flame, just a flicker.

Joe Niederberger