Comment 18 for bug 1666924

One response to this comment:

> there is no reason why anyone would want to go back on this.

It is pretty much essential now for support module releases to be compatible with more than one branch of Base. The guys supporting synApps don't mind having to make minor changes to their code to get it to build against new versions of Base, but they do want a new release to compile against older Base versions too — they *really* don't want to have a separate release branch of a module for each Base branch. They will use conditional compilation #if .. #else .. #endif blocks if necessary to make that work, but doing so does make the code ugly and harder to read.

In this case having to #define REC_TYPE for the new release won't break builds against the old Base, so I that should be fine. Having to make some method arguments const might be OK, but this has more of a chance of causing problems inside the method depending on how the arguments get used and what other routines they might get passed to.