Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc!csd4.milw.wisc.edu!lll-winken!uunet!seismo!esosun!ethan
From: ethan@esosun.UUCP (Ethan Brown)
Newsgroups: comp.lang.fortran
Subject: Re: Bogosity in Gould FORTRAN?
Message-ID: <468@kvasir.esosun.UUCP>
Date: 1 May 89 23:52:30 GMT
References: <7863@batcomputer.tn.cornell.edu>
Distribution: comp
Organization: SAIC, San Diego
Lines: 26
In-reply-to: lijewski@batcomputer.tn.cornell.edu's message of 1 May 89 20:48:21 GMT

In article <7863@batcomputer.tn.cornell.edu> lijewski@batcomputer.tn.cornell.edu (Mike Lijewski) writes:

	I have just had a run-in with Gould FORTRAN.  Apparently, Gould
   decided to OPEN files with the pointer at end of file as the default.
   So if you want to READ some data, you need to do a REWIND immediately
   after the OPEN.  On the two dozen or so types of computers I have run
   on, never have I run into this.  Have I just been lucky?  I would
   appreciate hearing from others who have been bitten by this?
	Gould says that since ANSI didn't explicitely say that the pointer
   to an OPEN'd file must be at the beginning of the file, that they can
   do this and still be ANSI.  Any comments?


Yes indeed.  I had the same unfortunate "feature" affect me when I ported
a seismic analysis code from UN*X to gould's version.  As you did, I just
went around and added rewind statements after each open.  

I will usually put a rewind statement after an open, and have had some people
remark that it's unnecessary.  Ha!  I'd sure like to know their rational
for OPENing files this way, though.

--
--Ethan Brown					...seismo!esosun!ethan
--Science Applications International Corp.
--Geophysics Division 
--