On Thursday 16 February 2012 16:23:28 Robin Burchell wrote: > On Thu, Feb 16, 2012 at 4:08 PM, David Faure <[email protected]> wrote: > > On Wednesday 15 February 2012 11:10:35 Lincoln Ramsay wrote: > >> Warnings have always been unconditional and will remain so. > > > > Not exactly. They can be disabled at compile time by > > -DQT_NO_WARNING_OUTPUT. > I almost wrote exactly that mail, but then I thought about the > context. The output may be disabled, but the call is always there, no?
No, not in Qt5: #if defined(QT_NO_WARNING_OUTPUT) # undef qWarning # define qWarning QT_NO_QWARNING_MACRO #endif and #define QT_NO_QWARNING_MACRO while (false) QMessageLogger().noDebug -- David Faure | [email protected] | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
