Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.13 $; site uiucdcs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!uiucdcs!goldberg
From: goldberg@uiucdcs.UUCP
Newsgroups: net.lang
Subject: Re: Why FORTRAN - (nf)
Message-ID: <26400016@uiucdcs.UUCP>
Date: Thu, 21-Jun-84 22:18:00 EDT
Article-I.D.: uiucdcs.26400016
Posted: Thu Jun 21 22:18:00 1984
Date-Received: Sat, 23-Jun-84 03:11:37 EDT
References: <2735@ecsvax.UUCP>
Lines: 15
Nf-ID: #R:ecsvax:-273500:uiucdcs:26400016:000:655
Nf-From: uiucdcs!goldberg    Jun 21 21:18:00 1984

#R:ecsvax:-273500:uiucdcs:26400016:000:655
uiucdcs!goldberg    Jun 21 21:18:00 1984

I have no complaint with FORTRAN's number-crunching abilities, but when it
comes to I/O the language is a big loss.  Just recently, on our RT-11 V5.1
system, we replaced one output subroutine in a graphics library which did its
I/O with a FORTRAN WRITE with the equivalent subroutine using RT-11 Syslib I/O.
This resulted in a speedup of something like 600%.  The net result was that the 
Prof. in charge bitched us out for not having done it 2 years ago, since it
only took 5 minutes to make the change.

				     Phil Goldberg
			    U of Illinois @ Urbana-Champaign
		      ...!{ihnp4,convex,pur-ee}!uiucdcs!goldberg
			       goldberg.uiuc@csnet.arpa