Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uunet!mcsun!ukc!axion!tharr!gombo
From: gombo@tharr.UUCP (Alun Jones)
Newsgroups: comp.lang.fortran
Subject: Re: VAX/VMS Fortran: Record length in BYTES
Message-ID: <1521@tharr.UUCP>
Date: 19 Dec 90 12:44:53 GMT
References: <5125.2767b5c5@cc.curtin.edu.au> <1990Dec17.173038.6222@eagle.lerc.nasa.gov>
Reply-To: gombo@tharr.UUCP (Alun Jones)
Organization: Power Microsystems Ltd
Lines: 30

I've got a different problem - but related - you might even say it's the
opposite of your problem.

I'm trying (valiantly) to translate from a VAX FORTRAN program onto a Unix
system.  I'm using AT&T's excellent freeware Fortran To C translator (it's
free, and tech support is quick - bug fixes by return of Email, usually),
and almost all of my problems come from the insistence of VMS Fortran to
align some things, but not others.

The program I'm converting uses a LOT of common blocks, with EQUIVALENCE
statements, but that's not my problem - f2c copes with that and warns me
when the COMMON alignment is screwy.  That I don't mind.

What is causing problems, though, is the use of files with a fixed record
length.  So far, I've just gone through and multiplied every RECL part of
an OPEN statement by 4, and the program appears to work now.  Is there any
quick check I can apply to see which OPENs will require this treatment?

Once again, thanks to AT&T for f2c - I'd recommend it to anybody who's
trying to get Fortran working on several types of Unix platform.

Hoping someone can help,
Alun.
~~~~~
-- 
Alun Jones - Unix Development Engineer - Welcom Software Technology Int'l.
My views are nothing whatsoever to do with the company I work for.
(That may be boring, but I feel safer for it.)

<-- tharr *free* public access to Usenet in the UK 0234 261804 -->