Strip AUTOSAR specific MACRO functions

[Letme]

AUTOSAR makes a mess as they define simple CONST as CONST function #define CONST(consttype, memclass) consttype const and even worse, they define FUNC macro function #define FUNC(rettype, memclass) rettype which developers then use as FUNC(void, FLSTST_CODE) FlsTst_Init(const FlsTst_ConfigType * FlsTstConfigPtr);.

So what I need to make is basically remove FUNC\( and , FLSTST_CODE\), but strippables is only able to remove words (I checked the code). Before I go all cowboyish inside the code to propose some wild change - I am hoping someone from the community has already done some unit testing on the AUTOSAR drivers?

[mvandervoord]

Are there recommendations on how anyone would like to see this sort of feature handled?

[Letme]

I would have strippables as regexp greedy potential.

My current workaround is to have #define CONST(consttype, memclass) consttype in the compiler_abstraction header file inside the ifdef TEST guard. It works but strippables would be easier.

[mvandervoord]

@Letme and the goal would be to reject CONST() and all its contents... or to remove CONST() but leave its contents?

[Letme]

With regexp as input you could do both right. Otherwise in my case I would need to get consttype out still, otherwise it has a problem. But my regexp would be to remove CONST($1, *) and just use $1 for example. I know this will be hard with backwards compatibility, but if you would put r' infront of the string, it would be treated as regexp inside the CMock.