Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!goanna!ok
From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
Newsgroups: comp.lang.fortran
Subject: Re: FORTRAN and (un)SAVEd vars
Keywords: FORTRAN 77, SAVE
Message-ID: <4849@goanna.cs.rmit.oz.au>
Date: 28 Feb 91 02:47:14 GMT
References: <1991Feb28.004447.3728@nas.nasa.gov>
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 13

In article <1991Feb28.004447.3728@nas.nasa.gov>, dueker@xenon.arc.nasa.gov (The Code Slinger) writes:
> Among other(!) problems, some variables in some of these routines expect to
> retain their values from invocation to invocation.  This, of course, is not
> guaranteed (except maybe on certain systems).
> 
> We'd like to find out if anybody knows of a program that will process
> FORTRAN 77 code and determine if any of the variables in a given subroutine
> should be SAVEd.

If your concern is just to get the code running, why not just SAVE
*all* the variables?
-- 
The purpose of advertising is to destroy the freedom of the market.