Ugh... I had something similar recently but much more painful to figure out - apparently googletest defines and and or (lowercase) as macros).
I started using googletest in a project with a moderate amount of inline assembly, and of course I got some thoroughly confusing error messages after the substitution replaced the and and or opcodes.
Anyway, I didn't know that push_macro and pop_macro existed, so I'll have to revisit my previous hack around that issue.
I started using googletest in a project with a moderate amount of inline assembly, and of course I got some thoroughly confusing error messages after the substitution replaced the and and or opcodes.
Anyway, I didn't know that push_macro and pop_macro existed, so I'll have to revisit my previous hack around that issue.