Re: [sigc] coexistence of Qt and sigc++?

["Murray Cumming" <murrayc murrayc com>]

> On Friday 28 July 2006 12:48, Murray Cumming wrote:
>> Yes, I've had this problem too. You might be able to #undef it.
>>
>> > Any tips for combining sigc++ and Qt would be appreciated.
>
> If it's undefined, Qt won't work properly, as it relies on that word :(.

Well, you'd have to be clever about where you define and undefine it.

But if moc processes source _before_ the normal preprocessor has run then
it shouldn't be affected.

> In my older case i ended up renaming my signal.emit() to signal.fire().

Well, you can use either
signal_something.emit();
or
signal_something()
so you might just try to avoid using the emit() alternative.

> Since sigc++ is so much more advanced than my home-rolled solution, i
> would prefer to use it, but i need eventual compatibility with Qt, so
> this is an important issue for me. (Granted, the bug is really in Qt,
> not sigc++.)


Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com