How to resolve it when class method and macro have the same name?

Question

I have encountered a problem when I was upgrading a class and need to import an external library.

For example, I am editing a class called CFoo, which has a public method SendMessage(). It works fine until I need to include a library - which contains a macro also named SendMessage(). It causes a complete mess to my current code because all part containing SendMessage() is being replaced by the macro.

I have found a similar question about macro naming collision: How do I avoid name collision with macros defined in Windows header files?

However in my case the public method name can't be changed as it is already released and used in other projects.

Is there a way not to use or include a specific macro, or to specify whether a macro or a method should be used when a function is called?

Thank you very much.

I believe you can call the member not the macro by using `(SendMessage)(args...)`. — user207421, Mar 21 '17 at 02:55
@EJP Even the method definition got replaced by the marco since I am actually including the library in the class header file. — user3545752, Mar 21 '17 at 03:03
Then you are certainly going to need `#undef` at least at that point. — user207421, Mar 21 '17 at 03:54

score 1 · Answer 1 · answered Mar 21 '17 at 03:42

1

If standard compliancy is not a requirement try the push_macro/pop_macro pragmas

#pragma push_macro("SendMessage")
#undef SendMessage
//your stuff
#pragma pop_macro("SendMessage")

It works on MSVC, GCC and CLANG

answered Mar 21 '17 at 03:42

xvan

4,554
1
22
37

score 0 · Answer 2 · answered Mar 21 '17 at 02:50

0

I have a vague way to resolve it.

Check using #ifdef..

If so, undefine it using "#undef" before calling your function.

answered Mar 21 '17 at 02:50

Pavan Chandaka

11,671
5
26
34

If I have multiple macro naming collision, do I have to `#undef` all of them? – user3545752 Mar 21 '17 at 02:53
Yes you do, and you don't need the `#ifdef`. – user207421 Mar 21 '17 at 02:55
I am not sure of any other way. Also I am not sure if namespacing works. Try it and see. – Pavan Chandaka Mar 21 '17 at 02:56
namespacing doesn't work, macros are resolved before the namespaces. – xvan Mar 21 '17 at 03:37

How to resolve it when class method and macro have the same name?

2 Answers2