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

Dave Thompson commented on DAFFODIL-2845:
-----------------------------------------

Added from commit comment for commit ff9ba411aefa8635831680f573c8f2670828421d, 
for tracking changes associated with this ticket. Per the comment this is a 
partial resolution.

    Refactor NodeInfo.PrimType. Add DFDLPrimType Java enum.
    Bunch of cleanups of NodeInfo dead or little-used code.
    optPrimType is now available on all TypeNodes and associated
    Kind Scala types. (eliminates list searching to find primType)

    Contributes to, but does not complete work on layers API.

 

> Layer improvements
> ------------------
>
>                 Key: DAFFODIL-2845
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2845
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.5.0
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Major
>             Fix For: 3.7.0
>
>
> Layers need access to DFDL properties at layer compilation time, and for some 
> (like delimiters) at runtime.
> Layers need to be able to create Schema Definition Errors at compile time and 
> at runtime, and need to be able to signal a variety of general Processing 
> Errors.
> (Currently,  throwing LayerNotEnoughDataException is the only way to cause a 
> processiing error. Other throws are all fatal.)
> Layer length kind 'explicit' should be deprecated. It is not needed since one 
> can create an element of specified length (lengthKind 'explicit',  
> 'prefixed', 'pattern' or 'endOfParent' when parent is of specified length) 
> surrounding a layer. 
> See also DAFFODIL-2843 and DAFFODIL-2844 which are also layer enhancements. 
> (Probably all should be fixed together along with firming up a SAPI Layer API)



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

Reply via email to