On Monday 16 March 2015 14:54:53 Thiago Macieira wrote: > On Monday 16 March 2015 21:05:41 Stephen Kelly wrote: > > Thiago Macieira wrote: > > > Because we want to benefit from the new code and remove the unnecessary > > > #ifndef and Q_UNUSED. If we don't change the current macro, then we > > > deprecate the old one and convert all the code to the new one > > > > You could deprecate the old behavior. > > > > #ifdef QT_BUILDING_QT || QT_DISABLE_DEPRECATED_BEFORE >= 0x050500 > > #define USE_NEW_ASSERT > > #endif > > > > #ifdef USE_NEW_ASSERT > > > > // ... > > > > #else > > > > // ... > > > > #endif > > We could do that. > > Opinions for or against?
I think it's a good idea, just like we have QT_USE_QSTRINGBUILDER, we could have QT_CHECK_ASSERT or something like that. -- Olivier Woboq - Qt services and support - http://woboq.com - http://code.woboq.org _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
