[
https://issues.apache.org/jira/browse/DAFFODIL-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943652#comment-16943652
]
Mike Beckerle edited comment on DAFFODIL-1060 at 10/3/19 3:56 PM:
------------------------------------------------------------------
Furthermore, when the expression is for a particular DFDL property, the
property name should be mentioned.
-This is particularly important for dfdl:occursCount expressions, because
unlike length expressions, they are "rooted" on the enclosing parent element,
not the child element. It's easy to have one too many "../" at the start of a
dfdl:occursCount expression.-
-The diagnostic message for dfdl:occursCount expressions should probably
address this topic somehow. like "Note dfdl:occursCount expressions start from
the enclosing parent element, not the element declaration where they appear.
Hence, the number of relative "../" steps at the start of the expression is one
fewer than for other expressions."-
was (Author: mbeckerle):
Furthermore, when the expression is for a particular DFDL property, the
property name should be mentioned.
This is particularly important for dfdl:occursCount expressions, because unlike
length expressions, they are "rooted" on the enclosing parent element, not the
child element. It's easy to have one too many "../" at the start of a
dfdl:occursCount expression.
The diagnostic message for dfdl:occursCount expressions should probably address
this topic somehow. like "Note dfdl:occursCount expressions start from the
enclosing parent element, not the element declaration where they appear. Hence,
the number of relative "../" steps at the start of the expression is one fewer
than for other expressions."
> More precise file and line number and character position information within
> DPath expressions
> ---------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-1060
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1060
> Project: Daffodil
> Issue Type: Improvement
> Components: Diagnostics, Front End, Usability
> Affects Versions: s15
> Reporter: Mike Beckerle
> Priority: Major
>
> Right now the Dpath expression parser doesn't provide detailed information
> about where sub-expressions are within an overall expression.
> Since expressions can be fairly large, finer granularity positions for
> diagnostic messaging would be a big improvement. Right now we can just say
> "this error occurred", and the position is just that of the entire expression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
