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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5a97e6705e234408
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-09-25 13:39:38 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: Expected bytes per sloc (semicolons) performance
Date: 25 Sep 2001 16:32:39 -0400
Organization: NASA Goddard Space Flight Center
Message-ID: <uy9n31060.fsf@gsfc.nasa.gov>
References: <matsw-2109011730340001@lsb-catv-2-p007.vtxnet.ch>
 <YZ1s7.46095$L%5.31186976@news1.rdc1.sfba.home.com>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 1001450040 133 128.183.220.71 (25 Sep 2001
 20:34:00 GMT)
X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov
NNTP-Posting-Date: 25 Sep 2001 20:34:00 GMT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
Xref: archiver1.google.com comp.lang.ada:13361
Date: 2001-09-25T20:34:00+00:00
List-Id: <comp.lang.ada>

tmoran@acm.org writes:

> Just glancing at a few things, 50 bytes/sloc doesn't seem unreasonable.
> 
> >>Rules about n bytes per sloc are just too processor, compiler, and
> >>coding style dependent to be useful.
> >
> >I would put a big emphasis on coding style here. If you use a lot of
> >generics, the code will be generated once for each instance in most
> >implementations.
>   But those implementations that share generic code would show the opposite
> effect.

Yes. So once again, bytes/sloc is a non-useful measure.

-- 
-- Stephe