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 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e5015e00941d1492 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-13 12:29:58 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!howland.reston.ans.net!agate!darkstar.UCSC.EDU!news.hal.COM!olivea!news.bu.edu!inmet!pes From: pes@inmet.camb.inmet.com (Paul Slonaker) Subject: Re: Magnavox consultant trashes Ada tools in IEEE Computer Message-ID: Organization: Intermetrics, Inc. References: Date: Thu, 13 Oct 1994 14:52:13 GMT Date: 1994-10-13T14:52:13+00:00 List-Id: I found the article to which Greg refers to be very interesting. I'm particularly interested in figuring out the impact of the various design decisions on the portability of the system, and less interested in the specific tool issues. Still, I couldn't let this particular lapse on the part of the author, and Greg's amplification of it, go without comment. In article , Gregory Aharonian wrote: > The October 1994 issue of IEEE COMPUTER has an article from Magnavox AFATDS >which does a pretty good job of effectively trashing Ada in a public forum. >Written by Joseph Skazinski (who obviously must have gotten burned by Ada >tools while working on AFATDS), the report illustrates the protectionist >weaknesses of the Ada Mandate vis-a-vis Ada vendors. > "... The compilation of all Ada and C source files took > nearly 4 days on the HP9000, less than a day on the RISC machines, > and close to a week on the Intel486 machines. (The equivalent > amount of C or C++ would take considerably less time; for example, > the GNU C++ compiler completed about 30,000 lines of code in about > 12 minutes on an Intel 486 SCO machine)." This is carelessness on the part of either the author or the editor. Nowhere in the article (as far as I could find), and certainly not in this part of it, does the author mention any size metrics for AFATDS. Not even a lines of code count, so that one could do an overly simple linear extrapolation to estimate how long it would take the GNU C++ compiler to compile the entire AFATDS. (Ignoring, of course, any differences between C and Ada lines of code.) >... my favorite, comparing a 12 minute compile time for some C code that is >equivalent to some Ada code that took a week to compile. Greg apparently misunderstood Skazinski's [incomplete] point, and draws the egregiously incorrect conclusion. Paul Slonaker Intermetrics, Inc.