On 10-01-26 9:03 , jmfbahciv wrote:
Alan Browne wrote:
On 10-01-25 8:43 , jmfbahciv wrote:

There have been a few bugs of this flavor on many systems in the
past. I vaguely recall one where the work around was to
split up the calculation statement. I don't remember the platform
nor the language nor the decade when it happened.

That's pretty common debugging in any day and age.

This is the first I've heard of the technique in a long time. However,
I live in a rarified atmosphere where this kind of stuff is SOP.

I'd do the same assuming I'd made a mistake in a statement. Once
working correctly, I'd leave well enough alone and move on.
Deadlines.

The other joy was moving FORTRAN from one platform to another and then
validating the code on the new platform ... tedious at best.

Unless the platforms' arithmetic are not consistent. Those are
really [NOT] "fun"....unless you have a really nice data set.
Then it could be fun.

Usually we had data that we could test with, this (in one case) included
a huge roll of punched paper tape. Fortunately I didn't do that one!

--
gmail originated posts are filtered due to spam.