You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2016/11/10 18:40:58 UTC

[jira] [Commented] (GEODE-2093) generated AbstractRegionEntry subclasses as part of build and do not check them in

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

Darrel Schneider commented on GEODE-2093:
-----------------------------------------

See GEODE-1785 for how these files are currently generated.

> generated AbstractRegionEntry subclasses as part of build and do not check them in
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-2093
>                 URL: https://issues.apache.org/jira/browse/GEODE-2093
>             Project: Geode
>          Issue Type: Improvement
>          Components: build
>            Reporter: Darrel Schneider
>
> Currently a large number of leaf subclasses of AbstractRegionEntry are generated manually by running a script. The generated source is under source control instead of being transient. A C preprocessor file is used to describe how to generate the files.
> It might be better to do this generation as part of the build instead of it being a manual step.
> It might be better for the generated source to be transient instead of under source control.
> A better, Java based way, may exist to deal with this instead of using the C preprocessor.
> One of the things to keep in mind would be how we would debug issues with this code and how will the IDEs support working with the code. Having the generated source checked in helps in both these areas but also can lead to developers directly modifying the generated source and not updating the cpp file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)