You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/08/05 15:35:00 UTC

[jira] [Closed] (DAFFODIL-2521) Schema compiler should insure all lazy eval is over with preSerialization call

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

Dave Thompson closed DAFFODIL-2521.
-----------------------------------

Commit cf8437e22432bc31d61ebdaafbd39c237d800afa was verified for Jira ticket DAFFODIL-2527 which has been closed.

> Schema compiler should insure all lazy eval is over with preSerialization call
> ------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2521
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2521
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Middle &quot;End&quot;
>    Affects Versions: 3.1.0
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Major
>             Fix For: 3.2.0
>
>
> Several places in our code base call preSerialization to insure that there is no lazy evaluation that could happen late, after compilation is supposedly over.
> The schema compiler should be responsible for making sure this is the case.
> This can be achieved by having the schema compiler invoke preSerialization of the parser & unparser objects before returning them.
> Then other uses of preSerialization in other places can be removed.
> There are some unit tests of the schema compiler that could be effected. There may be a need for test-only schema compiler interface to be invoked that does *not* do this preserialization call, so that unit tests can partly compile, but then make inquiries of the compiler data structures.



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