(j3.2006) Compilation cascades

[Van Snyder]

I wrote:

> That would explain why the .mod file would be different no matter what
> change I make.  Why would the .mod file be different only if I inserted
> a PRINT statement (or deleted them all)?

and Bill Long commented:

! Just a guess (by default we don't create .mod files), but the .mod file 
! might include the names of all the external symbols referenced.  A PRINT 
! statement will compile into a call to an external library procedure.

I have an otherwise-not-used function in each module that references a
parameter whose value is the CVS info for the module, to try to convince
optimizers to let that constant get into the object file.  I think I'll
add a PRINT statement to those functions.