There are quite a few codebases where the "override", "final", and "inline" keywords (as an example) are replaced with Macros such as PROJ_OVERRIDE or PROJ_FINAL in order to alter the export flags to certain platforms.
However, if you go to create the definition for a declaration of a function that contains these specifiers, VAX tends to copy them as it does not recognize what they actually substitute for.
Also, when generating inherited functions, VAX does not add the virtual keyword to the override functions.
It would also be nice to tell VAX to generate those functions with custom Macro defines/keywords.
We are considering a couple of changes that would help you here. We are considering allowing you to specify a macro that should be used instead of the "override" keyword, so I have added the idea of also replacing "final" and "inline" to the feature request:
We are also considering checking what macros found around functions expand to, so we can work out when they expand to keywords, and so treat them correctly: