[
https://issues.apache.org/jira/browse/DAFFODIL-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552885#comment-17552885
]
Steve Lawrence commented on DAFFODIL-2703:
------------------------------------------
Agreed. At the very least it should be an SDW, though an SDE seems more
reasonable. I can't think of a case where you would be okay with a fill byte of
the replacement character when the schema specifies some other code point. If
you want fill byte to be the replacement character, then you should explicitly
specify that as the fill byte.
> Unaligned RightFill does not unparse correctly
> ----------------------------------------------
>
> Key: DAFFODIL-2703
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2703
> Project: Daffodil
> Issue Type: Bug
> Components: Back End, Back End C-Generator
> Affects Versions: 3.3.0
> Reporter: Steve Lawrence
> Priority: Major
> Attachments: unalignedRightFill.tdml, unalignedRightFills.tdml
>
>
> See the attached unalignedRightFill.tdml file for reproducible tests.
> Data is a single byte. Only the most significant bit is actual data. The
> remaining 7 bits are RightFill region using a fillByte value of 0xF0. So the
> data should always unparse to X111 0000, where the value of X comes from the
> infoset.
> Note that runtime1 and runtime2 have different behaviors, neither of which I
> think is correct:
>
>
> *unalignedRightFill_01* (bit from infoset is 1)
> should unparse to 0xF0 (1111 0000)
> runtime1 unparses to 0xBF (1011 1111)
> runtime2 unparses to 0x9F (1001 1111)
>
> *unalignedRightFill_02* (bit from infoset is 0)
> should unparse to 0x70 (0111 0000)
> runtime1 unaprses to 0x3F (0011 1111)
> runtime2 unparses to 0x1F (0001 1111)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
