You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2023/03/06 17:26:00 UTC

[jira] [Closed] (DAFFODIL-2791) dfdl:occursIndex() returns wrong value when emptyElementParsePolicy="treatAsMissing"

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

Dave Thompson closed DAFFODIL-2791.
-----------------------------------

Verified the specified commits are included in the latest pull from the daffodil repository.

Verified, via review, changes identified in the commit comment were implemented. 

Verified the affected daffodil subproject sbt test suites executed successfully, including the added/uncommented test added in commit afb831e89cdddb07232b001fef70c015eb6e863d.

> dfdl:occursIndex() returns wrong value when emptyElementParsePolicy="treatAsMissing"
> ------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2791
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2791
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>            Reporter: Steve Lawrence
>            Assignee: Mike McGann
>            Priority: Major
>             Fix For: 3.5.0
>
>
> The dfdl:occursIndex() function currently returns the iteration number of the current array element. But if emptyElementParsePolicy="treatAsMissing", then we might not actually add an element but occursIndex will still increment.
> This function needs to take into account that the iteration count is not the same as the infoset count and only return the index of the current element in the infoset.
> We may also want to inspect other places where else we use the iteration count when we really want the infoset count.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)