You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2021/01/07 21:15:00 UTC

[jira] [Assigned] (DAFFODIL-1588) dfdl:nilKind 'literalValue' when the nil value contains delimiter characters

     [ https://issues.apache.org/jira/browse/DAFFODIL-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Beckerle reassigned DAFFODIL-1588:
---------------------------------------

    Assignee: Mike Beckerle

> dfdl:nilKind 'literalValue' when the nil value contains delimiter characters
> ----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1588
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1588
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, DFDL Language
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Minor
>
> There is no code to escapify the contents of the literalValue nil value during unparsing. 
> So if this nil value happens to contain a delimiter character, and the lengthKind is delimited, then nothing will escape the delimiter that is part of the nil value, and so we will not be able to parse the data again.
> An alternative to fixing this is just SDE, but since initiators/terminators/separators can come from runtime-valued expressions, a simple static check to rule this out isn't comprehensive but might be practical.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)