Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!cmcl2!lanl!jlg
From: jlg@lanl.gov (Jim Giles)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran vs C for computations
Message-ID: <3256@lanl.gov>
Date: 7 Sep 88 00:07:10 GMT
References: <1443@valhalla.ee.rochester.edu>
Organization: Los Alamos National Laboratory
Lines: 18

From article <1443@valhalla.ee.rochester.edu>, by davis@galaxy.ee.rochester.edu (Al Davis):
> 
> I have never seen a fortran compiler that had this option.  They all abort
> the program with a non-friendly message.  Any option that any fortran would
> have would necessarily be non-portable.
> [... other stuff about how C is better ...]

Anything C can do portably with library routines, Fortran can also do
portably with library routines.  Just because you haven't seen a Fortran
compiler that does X, doesn't mean X can't be done with Fortran.

The same goes for macros.  Anything C can do with macros, Fortran can
do with macros.  The only difference is that C makes macros part of the
language definition instead of part of the text editing environment
(where it belongs).

J. Giles
Los Alamos