PH Cleanup Routines

[Richard.Gambrell@xula.edu]

Peter Watt wrote (in part):
> Does anyone know of, or developed some PH cleanup routines.  For
> example, something to identify which internal procedures, temps and
> defines that are no longer referenced in the PH code.  I think we are
> in
> the same boat as many other companies, that our source has continued
> to
> grow over the years without ever having an efficient way to cleanup
> the
> code.  Someone recently suggested to me a cross-reference utility,
> that
> would help.

While we try to "clean up as we go" there are always cases that fall
through the cracks or we get in a hurry.  Still, there is nothing like
thoroughness in programming to prevent these kinds of things from
developing.

If you have Architect, at least on MPE (not sure about other platforms),
you could run the cross referencing documentation tools and dig the
"single hit per source file" reference to a name out of the database.

Adding "unreferenced variable" type warnings to PH would be nice, but I
wouldn't rate it very high on my top ten list of enhancement requests.

Richard Gambrell
Manager of Applications, Xavier U. of Louisiana, New Orleans, LA
work: richard.gambrell@xula.edu
home: rgambrel@acm.org