You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2021/12/06 20:03:00 UTC

[jira] [Resolved] (DAFFODIL-2592) Move the daffodil_program_version variable outside of generated_code.c

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

Steve Lawrence resolved DAFFODIL-2592.
--------------------------------------
    Resolution: Fixed

Fixed in commit 0029591b643c191ea0156dd830e848e7f8a3e728

> Move the daffodil_program_version variable outside of generated_code.c
> ----------------------------------------------------------------------
>
>                 Key: DAFFODIL-2592
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2592
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End C-Generator
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Currently, runtime2 writes the daffodil version to generated_code.c. We store some example generated_code.c files in the repo as examples, which means when we bump the Daffodil version number we must also remember to update these examples. That's not hard and we do have github checks to ensure they are updated, but it's one more thing to think about during the release process. We should move this version number somewhere else so we don't need to modify these example files for a version bump.



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