Prev: Is there a log framwork for fortran?
Next: How to INQUIRE if a directory is empty?
From: Richard Maine on 7 Mar 2010 21:04
Louis Krupp <lkrupp_nospam(a)indra.com.invalid> wrote:

> onateag wrote:
> <snip>
> > I tried to quickly put a STOP statement after the last WRITE, but this
> > didn't change either.
>
> Exactly what didn't change? If you still get a corrupt file, you might
> be closer to a very short program that reproduces the problem. And that
> could prove to be a big help.

Yes. Much my question. The objective of the STOP was not to solve the
problem, but to help in localizing it. If the program still reproduces
the problem, that's "good" in that you now have a smaller test case than
before (namely, you don't need to look at any of the program after that
STOP statement.)

--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Is there a log framwork for fortran?
Next: How to INQUIRE if a directory is empty?