🚀 go-pugleaf

I have written such a program, and use it primarily for checking
the number of parameters on subroutine calls and finding out
where entry points are. My program has just been for internal 
use here. The documentation is short and skimpy since I have been
available for hand-holding.

A more substantial, commercial product, is the Maintainability 
Analysis Tool, or MAT, sold for around $5K by Science 
Applications International Corporation. This analyzes Fortran source and 
produces a complete analysis of intra- and inter-module variable usage. 
It catches incorrect number and type of parameters, as well as many 
cases of dubious usage. It runs on many systems, is supported, and, in 
my opinion, does a good job. If you are given the task of maintaining 
someone else's Fortran program (or even your own program), MAT will save 
you a large amount of work, and will probably catch some errors in a 
supposedly debugged program. (When I ran MAT on mine, it caught two 
errors that had gotten past me.)

For information about MAT, contact:
	Gerald M. Berns
	Science Applications International Corporation
	2361 Jefferson Davis Highway, Suite 320
	Arlington, VA 22202
	(703) 979-5900

I could make my program available (both source and object), but with
no help and the usual "this program may or may not do anything"
disclaimer.

It is my feeling that MAT is a far more useful tool, and well worth
the cost.

Martin Cohen (mcohen@nrtc.northrop.com)
Northrop Research and Tech Center
One Research Park
Palos Verdes Peninsula
CA 90274
(213) 544-5373