Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!lanl!jlg
From: jlg@lanl.gov (Jim Giles)
Newsgroups: comp.society.futures
Subject: Re: C's sins of commission (was: (pssst...fortran?))
Message-ID: <63475@lanl.gov>
Date: 19 Sep 90 21:42:52 GMT
References: <4905@uqcspe.cs.uq.oz.au>
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 13

From article <4905@uqcspe.cs.uq.oz.au>, by brendan@batserver.cs.uq.oz.au (Brendan Mahony):
> [...]
> Yes you are. You are leaving out memory mapped I/O and operating system
> vectors and other disgusting cludges that make the computing world go
> round. Other than than you are spot on!

Perhaps you can be kind enough to point out the reason I need pointers
(or anything else that's not on my list) to provide the functionality
you mention.  The first memory mapped I/O I ever used was done in Fortran.
And, not an extended Fortran either - passing arrays with call-by-reference
is quite adequate to tell the system where my I/O buffer is to be.

J. Giles