Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!netcomsv!holen From: holen@netcom.COM (Victor Holen) Newsgroups: comp.software-eng Subject: Re: OOP in the "real world" Message-ID: <1991Jun29.073150.8070@netcom.COM> Date: 29 Jun 91 07:31:50 GMT References: <1991Jun21.200139.14639@den.mmc.com> <1991Jun26.221144.6532@bellcore.bellcore.com> Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} Lines: 23 In article <1991Jun26...> bytor@ctt.bellcore.com (Ross Huitt) writes: > >Anybody else have any numbers they would like to share? > Sure. 1,2,3,4... :) Also, In a large CAD system, using Mainsail (OOL) 350 K lines source = 5,503 K bytes compiled (comments included -sorry :( ) = 5,503 K bytes which gives ~ 16 bytesCompiled/lineSource on averge, and differed from one large sub-project to another from 10 bytesCompiled/lineSource to 32 bytesCompiled/lineSource. Some reasons for wide variations: Coding styles: number of comment lines, number of statements per line (sic) Use of macros versus functions. Large use of common utility macros (interactive graphics project) versus much less in algorithms projects. To make more sense, one could write a program to count executable statement after macro or inline procedures expanded,... but one didn't -- e e-mail: holen@netcom.com -- e-mail: holen@netcom.com