I'm a little worried about conflicting with existing macros in older code, mainly with Q

I'm a little worried about conflicting with existing macros in older code, mainly with Q

was Q() used differently in the past?

I searched CBA and ace and didnt find any macro thats defined that way.

I can make each a #ifndef if needed or #ifdef #undef #define

I don't think any of those macros are useful. If a mod itself wants them, they could always define them. This is just obscuring things it too much from my POV.

I don't think any of those macros are useful. If a mod itself wants them, they could always define them. This is just obscuring things it too much from my POV.

Just my opinion but cba already using Q in macro's like QGVAR/QQGVAR etc.for me its simply the most logical step to fill the gap and actually implement Q/QQ by itself as well as combined with others like QADDON

I don't see the point in shortening the general QUOTE to Q, I think it'll be less readable and the 4 character space savings don't matter.

I could see doing QADDON though, in the same way as QGVAR, as
#define QADDON QUOTE(ADDON)

moved Q,QQ into seperate PR #1759

probably should've moved these ADDON macros to another PR, so the comments regarding Q, QQ stayed relevant

probably should've moved these ADDON macros to another PR, so the comments regarding Q, QQ stayed relevant

fair enough, but now this one at least has some momentum and gets merged maybe