Q_SLOTS, Q_SIGNALS or slots, signals ?

[opengpu]

Q_SLOTS, Q_SIGNALS or slots, signals ?
what should i write in my app?

[Dariusz]

I went with Q_SLOTS/Q_SIGNALS as I had conflicts with other libraries when using signals/slots... so I would suggest going with Q_SIGNALS...

[sierdzio]

These macros are synonyms (no functional differences), so it's purely up to your taste. If you get conflicts like @Dariusz you have to go with Q_*. In other cases - I'd argue that signals looks much better than Q_SIGNALS - but as said, it does not matter which you choose.

[Buckwheat]

@sierdzio said in Q_SLOTS, Q_SIGNALS or slots, signals ?:

ave to go wi

@Dariusz

I just always use Q_SLOTS/Q_SIGNALS and Q_EMIT. This is easy to see in code and easy to search for in an IDE. I find after all my years I am about the future development and others being able to quickly glean information from looking at the code as to what is compiler and what is extra-ordinary.