Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: C vs. FORTRAN
Message-ID: <225800204@uxe.cso.uiuc.edu>
Date: 6 Aug 89 14:45:00 GMT
References: <3288@ohstpy.mps.ohio-state.edu>
Lines: 22
Nf-ID: #R:ohstpy.mps.ohio-state.edu:3288:uxe.cso.uiuc.edu:225800204:000:962
Nf-From: uxe.cso.uiuc.edu!mcdonald    Aug  6 09:45:00 1989



>The odds are pretty good that somebody asking about relative code
>efficiency is worrying about the wrong issues in choosing a
>programming language.

I don't understand this statement! Somebody serious about relative
code efficiency (and mentioning Fortran) probably has a big program.
They may be worried that it would cost $20000 of cpu time in
one language instead of $40000 in another. This isn't important?
OR they might be worried that one would take 300 microseconds to
process a piece of incoming data, and another language might take
600 microseconds, and the data is expected to arrive at 400 microsecond
intervals.

If efficiency matters at all then it usually is the MOST important issue.
Sometimes it is even more important than getting the "right" answer (!),
as in using a some math function (say sin(x)) that is only good to three
significant digits, just to be faster, rather than in using a slower
but more accurate routine..

Doug McDonald