From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Newsgroups: comp.lang.ada
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!linus!linus!linus!mbunix!eachus
From: eachus@aries.mitre.org (Robert I. Eachus)
Subject: Re: LOC Lines of Code debate
In-Reply-To: Kevin_Miller.D76_CENTRAL@qmgate.mitre.org's message of Fri, 29 Mar 1991 19:37:45 GMT
Message-ID: <EACHUS.91Apr1152227@aries.mitre.org>
Sender: news@linus.mitre.org (News Service)
Nntp-Posting-Host: aries.mitre.org
Organization: The Mitre Corp., Bedford, MA.
References: <"910326054349.71660.412.CHE55-1"@CompuServe.COM>
	<785.27f18ef4@vger.nsu.edu> <1991Mar29.193745.21498@linus.mitre.org>
Date: 1 Apr 91 15:22:27
List-Id: <comp.lang.ada>



     How about the number of documented decisions made? (I'd count
undocumented too if I could figure a reasonable way to do so.)  One of
the reasons I find that "productivity" in non-comment LOC is so much
lower in Ada package specifications, is that the interface (and stated
listed pre- and post- conditions make the actual implementation of
many bodies no brainers.  Use of a design language like Anna or Byron
should make it fairly easy to pick up and count such decisions.

     A simpler approximate measure (for well written Ada) is the
number of declarative items, since each type, task, subroutine, or
object declaration tends to embody about the same number of design
decisions.  (Poorly written code on the other hand tends to have lots
of "junk" variable declarations--many often unused.)


--

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...