Bug #4244
Updated by Greg Shah over 4 years ago
In statements like <code>DISPLAY expression @ field.</code> the conversion does sometimes add either a bad format to the field or multiple formats.respected.
It should be also taken in consideration the explicit format when a FrameElement is created, while this overrides the default format defined in the UI class.
In addition to this, the format length should be computed accordingly, while there are cases in which the format is correct and the display field is either too short or too long.
Cross data types as well should be managed properly, as if the expression and the field do have different data types, either an error is thrown or an incorrect value is printed.
Finally, a comprehensive set of tests, with combinations of data types for the expression/field, is required in order to detect a proper fix.
It should be also taken in consideration the explicit format when a FrameElement is created, while this overrides the default format defined in the UI class.
In addition to this, the format length should be computed accordingly, while there are cases in which the format is correct and the display field is either too short or too long.
Cross data types as well should be managed properly, as if the expression and the field do have different data types, either an error is thrown or an incorrect value is printed.
Finally, a comprehensive set of tests, with combinations of data types for the expression/field, is required in order to detect a proper fix.