(j3.2006) exception message on termination

[Malcolm Cohen]

The only complaint we got was for reporting underflow, so we added an option to 
suppress that one.

We never report inexact.  I agree it is completely pointless to report inexact, 
in my opinion it was an oversight not to make than an exception to the reporting 
rule.

Cheers,

-----Original Message----- 
From: Robert Corbett
Date: ?? 25?6?12? 12:59
To: j3
Subject: (j3.2006) exception message on termination

Can we delete the second and third sentences of paragraph 2 in Clause 8.4 in the
upcoming revision?  They state

      If an exception (14) is signaling on that image,
      the processor shall issue a warning indicating
      which exceptions are signaling; this warning
      shall be on the unit identified by the named
      constant ERROR_UNIT (13.8.2.8).  It is recommended
      that the stop code is made available by formatted
      output to the same unit.

Sun FORTRAN 77 produced such output.  It was a constant source of complaints
from users.  As bad as Sun FORTRAN 77 was in this regard, it did not report
inexact exceptions, as is required by the text of the standard.

Robert Corbett
_______________________________________________
J3 mailing list
J3 at mailman.j3-fortran.org
http://mailman.j3-fortran.org/mailman/listinfo/j3

________________________________________________________________________
This e-mail has been scanned for all viruses by Star.
________________________________________________________________________

-- 
................................Malcolm Cohen, Nihon NAG, Tokyo.