(j3.2006) J3 Fortran interp letter ballot #22 - due 19-Nov-2010
Mon Oct 18 02:37:12 EDT 2010
Malcolm Cohen wrote:
> Van Snyder wrote:
>> -C- --- F03/0030 IEEE divide by zero
>> Change "not true" to "false" because "not true"
>> includes "undefined".
> No it doesn't.
>> This leaves the program non-conforming
>> (presumably because the processor is defective) if the result
>> is undefined.
> Being undefined is a property of a variable. IEEE_SUPPORT_DATATYPE is not a variable, it is a function. A function reference (other than a pointer-valued function) returns a value of the type. That does not include the concept of being undefined.
The "result variable" of a function is a variable. I found where the
standard requires a value to be assigned to a function's result
variable. I suspect you're right that there is not a
standard-conforming way to do that, and leave the result undefined.
More information about the J3