[ 
https://issues.apache.org/jira/browse/DAFFODIL-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661445#comment-16661445
 ] 

Michael Beckerle commented on DAFFODIL-1056:
--------------------------------------------

To clarify: We used to get "Runtime Schema Definition Error", and now we get 
just "Schema  Definition Error" eventhough it is detected at runtime. The term 
"Runtime" has been lost because code is being shared across compile and 
runtime, so the distinction is being lost. 

Very minor issue. 

> DPath: Decreased precision - Compile Time vs Runtime SDE
> --------------------------------------------------------
>
>                 Key: DAFFODIL-1056
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1056
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Diagnostics, Usability
>    Affects Versions: s15
>            Reporter: Jessie Chab
>            Priority: Major
>
> From Mike: Yeah, this is a decrease of precision, but the new DPath 
> implementation changes came with some loss of proper categorization. 
> Basically, some areas where the code was clearly compilation time or clearly 
> runtime have been replaced by common code that is used in both cases, and 
> that code issues an SDE. Nothing recaptures this and converts it into a 
> "Runtime" SDE currently.
> So I'd say it's a bug that we've lost this precision, because I like having 
> the separation where SDEs that are detected to occur at runtime are 
> explicitly identified. But the DFDL spec doesn't say when anything has to be 
> detected.
> So if we view the test as testing the DFDL spec requirement, then making the 
> test less precise is ok. If we view the test as verifying our desired behavor 
> for Daffodil, then the loss of precision is a bug.
> I suppose really there are two tests then.... I would prefer not to fix this 
> particular issue right away however.
> Changes in diagnostic behavior are probably the biggest observable places 
> where behavior will have changed
> Associated test(s):
> test_variableRefError



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to