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 2022/04/14 19:26:00 UTC

[jira] [Created] (DAFFODIL-2691) parse errors on debug traces when there is nothing wrong

Mike Beckerle created DAFFODIL-2691:
---------------------------------------

             Summary: parse errors on debug traces when there is nothing wrong
                 Key: DAFFODIL-2691
                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2691
             Project: Daffodil
          Issue Type: Improvement
          Components: Diagnostics
    Affects Versions: 3.3.0
            Reporter: Mike Beckerle


User reports looking at a debug trace and seeing a parse error associated with internal behavior of Daffodil. 

The specific situation is for a nillable element. The parser is trying the nil representation, then it issues a parse error and backtracks to try the normal representation. This shows up on the diagnostic output as a parse error associated with the nilled element, which parsed fine, just wasn't nil. 

Really we shouldn't use regular failure backtracking internally like this, as it misleads users. Really we need a nilledElement combinator that orchestrates trying the nil representation and then tries the other representations if that doesn't work. The point being to eliminate user-visible backtracking and diagnostics activity. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)