next »

[InfiniteStateMachine]

So I'm currently using 2 different libraries that both have a function called "connect" one is a library that brings in the windows.h header and the other is qt.

Unfortunately when I try to use the connect function in Qt I get a compile error that essentially says it has the wrong number of arguments because it expects the arguments for the windows command.

Now in C++ this would be resolved with namespaces. Is there any way to resolve this issue? I've tried using the global namespace operator (aka ::connect) but that did not resolve the situation.

[eigenbom]

i think i recall that Qt has a flag that forces it to use a more verbose form of connect(), like QT_SIGNAL_CONNECT(...) or something

[Evan Balster]

This sort of thing can be hugely problematic -- I've had to deal with link errors in situations like this and it's generally very nasty.  C API developers need to remember to prefix and C++ API developers need to remember to use namespaces.

You might use more specific headers than windows.h -- it's sort of infamous for being a major source of namespace pollution.  Its min() and max() macros are particularly bad.

[InfiniteStateMachine]

unfortunately it's not me who calls in the windows.h file. It's the commercial library the company I work for uses unfortunately.

Thanks for the tip eigen, I'll look into that.

[eigenbom]

np good luck

[ThemsAllTook]

If nothing else works, you can potentially wrap one of your #includes in #define connect(...) some_other_name(...) ... #undef connect to rename one of the connects. I'm not entirely sure you won't run into problems at link time, though...

[InfiniteStateMachine]

Finally figured it out. Apparently connect is defined globally as a c function but also as a static function of QObject.

Heh many of my google searches for this problem resulted in this thread :D