You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several issues with the parsing of numeric fields with a fixed width and/or precision. The common pattern for all of them is that the width/precision specification is applied inconsistently for different numeric representations (i.e. decimal, hexadecimal, etc):
As per the documentation: Width specifies a minimum size and precision specifies a maximum.
In all of the cases, we both have a width and a precision field. However, in the first case the parsing of the first number field consumes four hexadecimal digits despite the fact that the precision should specify a maximum field length. What is more, we also have a width specifier which says that the numbers should be at least two digits long, and yet the latter two numbers are represented using only one digit.
The rest of the cases demonstrate the same issue with the width specifier.
The text was updated successfully, but these errors were encountered:
There are several issues with the parsing of numeric fields with a fixed width and/or precision. The common pattern for all of them is that the width/precision specification is applied inconsistently for different numeric representations (i.e. decimal, hexadecimal, etc):
As per the documentation:
Width specifies a minimum size and precision specifies a maximum.
In all of the cases, we both have a
width
and aprecision
field. However, in the first case the parsing of the first number field consumes four hexadecimal digits despite the fact that theprecision
should specify a maximum field length. What is more, we also have a width specifier which says that the numbers should be at least two digits long, and yet the latter two numbers are represented using only one digit.The rest of the cases demonstrate the same issue with the
width
specifier.The text was updated successfully, but these errors were encountered: