[DFDL-WG] Behavior of nilKind literalValue with respect to binaryNumberRep of packed
Bradd Kadlecik
braddk at us.ibm.com
Tue Apr 14 14:59:28 EDT 2020
I think there is a problem when the literalValue is left-justified for
binary data such as packed decimals. This seems problematic because a "0"
value might be indicated by having the last byte be 0x0C for a signed
numeric while a nil value might be desired to be understood by having the
last byte be a 0x0F. In both cases, all preceding bytes are 0x00. In the
case that the packed decimal is of variable length, there seems no way to
represent this nil value unless it is understood that the fillByte is used
for the area preceding the NilElementLiteralContent. Apologies if I might
of missed some clarification made regarding this.
Regards,
Bradd Kadlecik
z/TPF Development
Phone: 1-845-433-1573 2455 South Rd
E-mail: braddk at us.ibm.com Poughkeepsie, NY
12601-5400
United States
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/dfdl-wg/attachments/20200414/1ad304df/attachment-0001.html>
More information about the dfdl-wg
mailing list