Changes between Initial Version and Version 1 of Ticket #269
- Timestamp:
- 12/19/2021 09:39:18 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #269 – Description
initial v1 1 1 Test program fld59 accepts a fixed-point string with optional exponent sub-field, and uses the PL/I convert built-in to change this string to a float dec(59) data type. 2 2 3 Results of using this program to convert strings within and just outside of the support exponent range for float dec(59) show correct signaling of exponent overflow and underflow when outside the supported range: -128 <= exponent <= +127.4 3 Results of using this program to convert strings within and just outside of the support exponent range for float dec(59) show correct signaling of exponent overflow and underflow when outside the supported range: 4 -128 <= exponent <= +127. 5 5 6 6 {{{ … … 56 56 onsource: "1F129" onchar: "9" onchar_index: 5 57 57 }}} 58 59 Because oncode values are just numbers having no names, it isn't clear whether the wrong oncode number is associated with F-exponent underflow and overflow; or the correct oncode is being used but the message table containing the description associated with those encode values (oncode_messages_$) is wrong.
