Prev: Variable scope: how fortran deals with undeclared variables in subroutines?
Next: how to use MODIFYMENUROUTINEQQ
From: Richard Maine on 17 Feb 2010 16:49
dpb <none(a)non.net> wrote:

> Then again, there's always a possibility that the original coder didn't
> get everything initialized and relied on either a compiler switch to
> zero memory or the behavior of a specific compiler that did so.

And then there is the previously unmentioned possibility that it might
just plain be a bug in the code. :-( Insufficient data to tell, but
having lots of undeclared variables increases the odds.

--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
 | 
Pages: 1
Prev: Variable scope: how fortran deals with undeclared variables in subroutines?
Next: how to use MODIFYMENUROUTINEQQ