[deepsterblue]

Just a suggestion, but perhaps it would be useful to have the Foam version as a compile-time macro. For example, something like this for OF-1.5:

#define FOAM_MAJOR_REVISION 1
#define FOAM_MINOR_REVISION 5

Or something on similar lines (Maybe passed in to g++ with a -D option). Considering how member functions change over revisions, (like faceOwner instead of allOwner in polyMesh, for instance), backward compatibility is sometimes an issue. I agree that it makes code uglier because of #ifdefs all around the source code, but it might be handy to have...

[olesen]

Originally Posted by deepsterblue

Just a suggestion, but perhaps it would be useful to have the Foam version as a compile-time macro. For example, something like this for OF-1.5:

#define FOAM_MAJOR_REVISION 1
#define FOAM_MINOR_REVISION 5

wmake already has/had a PROJECT_VERSION defined as major, 3 digits minor and 3 digits revision.
For example, 1.5 == -DPROJECT_VERSION=1005000.
Unfortunately this breaks down horribly when versions contain non-digits (eg, like 1.5.x). I would thus avoid using it at all.

IMO the better method is to keep your code up-to-date with the latest developments and use branching within git if you also need to maintain code for legacy versions. This is not only much cleanier to read than piles of #ifdefs, but also avoids strange and possibly hard to trace bugs. For example, if you'd moved from 1.5 to 1.5.x, the wrong chunk would get evaluated here:

#if PROJECT_VERSION >= 1005000
chunk1 ...
#else
chunk2 ...
#endif

I think the need for using PROJECT_VERSION disappeared with the introduction of git for version control. I wouldn't be surprised if PROJECT_VERSION disappeared in a future version, but you can copy the same idea in your own Make/options if you'd like.

[olesen]

Originally Posted by olesen

IMO the better method is to keep your code up-to-date with the latest developments and use branching within git if you also need to maintain code for legacy versions. This is not only much cleanier to read than piles of #ifdefs, but also avoids strange and possibly hard to trace bugs.

Someone brought this old thread back to my attention, so I figured it could make sense to update it.
The OPENFOAM compiler define, which is a 4-digit value corresponding to the api version, can be used for transitional features etc. Eg,

#if (OPENFOAM >= 1812)
Info<< "using some OpenFOAM-v1812 version" << nl;
#else
Info<< "using some other version" << nl;
#endif

The value is defined within the wmake rules, so it should correspond to the currently active OpenFOAM environment/version.