Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.11.1
-
None
-
60c70e4eff (qt/qtbase/dev) 60c70e4eff (qt/tqtc-qtbase/dev) bd867924b7 (qt/qtbase/6.2) bd867924b7 (qt/tqtc-qtbase/6.2) fb6c21dbc9 (qt/qtbase/6.3) fb6c21dbc9 (qt/tqtc-qtbase/6.3)
Description
Both defines QT_NO_SIGNALS_SLOTS_KEYWORDS & QT_NO_KEYWORDS are in use out there in Qt-based software projects. Yet they are not mentioned anywhere in the Qt documentation (by what I saw and my search skills gave me).
The only semi-official mention of the presence of those definitions I found is
https://www.kdab.com/kdab-contributions-to-qt-5-0-part-5/
The only related info I could find in the Qt documentation itself is about the flag to use with qmake (CONFIG += no_keywords), http://doc.qt.io/qt-5/signalsandslots.html#using-qt-with-3rd-party-signals-and-slots . Which misses a variant for the no-signals-slots-only case.
And there is mention of the same qmake flag with the docs for the macros Q_SIGNALS, Q_SLOT, Q_SLOTS (http://doc.qt.io/qt-5/qobject.html#Q_SIGNALS ff.).
To be able to reason about the use of those definitions in own code, to fellow developers or managers or students, it would be good to have some official statement in the Qt documentation (e.g. on the page http://doc.qt.io/qt-5/signalsandslots.html or with the QObject signal/slot macros).
Or get an official statement here saying that those defines are unsupported and should be expected to disappear or change their behaviour any time in future versions (which would be sad, but one would be prepared ).