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 09:08:24 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!feed.textport.net!out.nntp.be!propagator-SanJose!news-in-sanjose!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc1.sfba.home.com.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Expected bytes per sloc (semicolons) performance References: X-Newsreader: Tom's custom newsreader Message-ID: Date: Tue, 25 Sep 2001 16:08:24 GMT NNTP-Posting-Host: 24.7.82.199 X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.sfba.home.com 1001434104 24.7.82.199 (Tue, 25 Sep 2001 09:08:24 PDT) NNTP-Posting-Date: Tue, 25 Sep 2001 09:08:24 PDT Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: archiver1.google.com comp.lang.ada:13344 Date: 2001-09-25T16:08:24+00:00 List-Id: 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.