Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!unmvax!ariel.unm.edu!ghostwheel.unm.edu!john
From: john@ghostwheel.unm.edu (John Prentice)
Newsgroups: comp.lang.fortran
Subject: Re: FORTRAN vs C
Message-ID: <1990Nov29.051013.19149@ariel.unm.edu>
Date: 29 Nov 90 05:10:13 GMT
References: <1990Nov26.171823.4008@isc.rit.edu>
Sender: news@ariel.unm.edu (USENET News System)
Organization: Amparo Corporation,  Albuquerque, NM
Lines: 17

In article <1990Nov26.171823.4008@isc.rit.edu> jav8106@ritvax.isc.rit.edu writes:
>
>Let's face it -- C has all kinds of bells and whistles, such as structures,
>unions, boolean manipulations, dynamic allocation, etc., but it is a real dog
>to work with. For one thing, it simply isn't as portable as FORTRAN. A short on
>one machine is something else on another. The whole thing was really a
>heinous hack job foisted off on a bunch of computer-science types who simply
>had to have those bells and whistles -- and took it to heart in spite of its
>glaring inadequacies, which were different from FORTRAN's glaring inadequacies.
>

I would like to quote Jim Giles concerning essentially this point.  Fortran's
sins are sins of omission.  C's sins are sins of commission.

John Prentice
Amparo Corporation
Albuquerque, NM