Re: This is weird: the exception points me to a commented-out statement

On 20-Aug-2014 15:27 -0500, James H. H. Lampert wrote:

A character representation of a numeric value is in error.
Function check. RNX0105 unmonitored by WTAPISRR at statement
0000007540, instruction X'0000'.

But when I look at a fresh compilation listing of the source
member, compiled (near as I can tell) over the same files, I see:

7539 // endif;
7540 // endif;
7541 // else;

This doesn't make any sense. Why would an exception be giving me a
reference to a commented-out line?

A newly recompiled executable\program is not necessarily going to be /the same as/ the existing executable that was compiled sometime in the past. Even if the [primary] source did not change, referenced objects and included sources could have changed, plus the macro processors and [pre]compiler(s) could have changed.

The listing from the compile that created the failing executable really should have been maintained, and that listing viewed for the statement number provided by the message, to properly determine the point of failure. Or debug information could be left in the executable\program so that the debugger can show a listing view for the executable object that resides on the system where the failure occurs.

Effectively, the "near as I can tell" just _doesn't cut it_ in such situations :-(