Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!LLL-MFE.ARPA!CUNNINGHAMR%HAW.SDSCNET
From: CUNNINGHAMR%HAW.SDSCNET@LLL-MFE.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Number crunching
Message-ID: <8607150932.AA15928@ucbvax>
Date: Tue, 15-Jul-86 05:33:00 EDT
Article-I.D.: ucbvax.8607150932.AA15928
Posted: Tue Jul 15 05:33:00 1986
Date-Received: Tue, 15-Jul-86 19:38:42 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: info-vax@sri-kl.arpa




Number crunching in FORTRAN vs. C.

In geophysical---and many other---applications, `number crunching' means
dealing with multi-dimensional arrays of complex (not real) numbers.
Commonly-used routines (e.g., FFTs and similar transforms) effectively
have to be coded so that array bounds are not hard-wired at compile time.

The FORTRAN syntax involved tends to be fairly straightforward, reasonably
mirroring the algorithms involved.

C code for such things gets very complicated early on and it's easy to
lose the feel of what the algorithms are really doing.  My personal
opinion is that too many details have to be buried too deeply in such code.