We had a similar issue with an in-house signal/slot module conflicting
with Qt's 'emit' keyword
We also use - DQT_NO_KEYWORDS and use the upper case versions for those
signals becomes Q_SIGNALS, slots becomes Q_SLOTS, emit becomes Q_EMIT, etc.
The Qt library sources work with the upper case versions too, btw
Maybe this could work for you as well.
> Peter wrote on Friday, March 19, 2010 9:19 AM:
>> Is there any way to get through the moc generation without
>> conflicting with boost::signals?
> An exhaustive 10 second google research(tm) came up with the following:
> FAQ: "3. How do I get Boost.Signals to work with Qt?"
> Cheers, Oliver
Qt-interest mailing list