You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2020/07/17 12:07:00 UTC

[jira] [Updated] (DAFFODIL-2371) Multiple discriminator behavior is not correct

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

Steve Lawrence updated DAFFODIL-2371:
-------------------------------------
      Component/s: Back End
    Fix Version/s: 3.0.0

Tests showing incorrect behavior added in commit 16f70fb2027eec5b30af75fd011669dad2a3b808

> Multiple discriminator behavior is not correct
> ----------------------------------------------
>
>                 Key: DAFFODIL-2371
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2371
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>            Reporter: Steve Lawrence
>            Priority: Major
>             Fix For: 3.0.0
>
>
> When a discriminator evaluates to true, Daffodil always resolves the nearest in-scope point of uncertainty, even if it has already been resolved by another discriminator. This means if there are multiple discriminators, we may resolve the same PoU repeatedly, essentially making true discriminators no-ops. 
> Based on recent clarifications by the DFDL-WG, a descriminator that evalutes to true should instead resolve the nearest *unresolved* point of uncertainty. This means multiple discriminators evaluating to true will result in multiple PoU's being resolved.



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