(j3.2006) exception message on termination

[Van Snyder]

Bill Long wrote:
>
>
> On 6/12/13 12:28 PM, Van Snyder wrote:
>> Bill Long wrote:
>>> Perhaps instead of having the current requirement, we could add a
>>> IEEE_PRINT_EXCEPTION_SUMMARY intrinsic subroutine that the user could
>>> call if they wanted this sort of output, and disconnect the output
>>> from STOP.
>>
>> A very long time ago (i.e., for f95), a block-structured
>> exception-handling mechanism was proposed, but fell onto the
>> cutting-room floor.
>>
>> Absent that, how would a program capture a STOP in, say, the main
>> program, and call the IEEE_PRINT_EXCEPTION_SUMMARY subroutine?
>
> I was thinking much simpler - the programmer just inserts the CALL 
> before the STOP statement.  An industrious programmer could, of 
> course, write such a subroutine using the existing facilities.

I think Bill means "before every STOP statement."  If the program stops 
for another reason, say deallocating a disassociated pointer, or 
computing the logarithm of zero, it's a bit hard to insert the call.

>
> Cheers,
> Bill
>
>>
>