From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 15 Oct 92 12:21:44 GMT
From: cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!mlb.semi.har
ris.com!dw3g!smccoy@ucbvax.Berkeley.EDU  (Scott McCoy)
Subject: Re: Assy/Ada SLOC ratio;What's an Ada SLOC?
Message-ID: <1992Oct15.122144.11657@mlb.semi.harris.com>
List-Id: <comp.lang.ada>

In article <1992Oct14.121432.10919@aplcen.apl.jhu.edu>, dlc@ddsdx2.jhuapl.edu (
Dave Collard x7468) writes:

[...code example deleted...]

|> 
|> IMHO, any method that depends on semicolons for counting
|> lines of code is pretty useless.
|> 

You've hit on a key point here -- just what do want your 'SLOC'
metric to measure?  Size?  Complexity?  Depending upon your
answer, different SLOC methods may be appropriate.

In the years I've been working in the Ada industry, I've never
seen a consensus for an Ada SLOC computational method.

In the past, I've used 'every non-blank, non-comment line is
a LOC'.  Note that this method is highly depend upon programming
and formating style.  I know that.  But it's a simple way to
count, and if you're consistent, then the data can be meaningful.

Just my $0.02.
-- 
Scott McCoy	Harris ISD	Opinions expressed are my own.
Staff Eng - SW	Internet: 	smccoy@dw3g.ess.harris.com