On Thursday, 13 October 2022 06:50:06 PDT Edward Welbourne via Development wrote: > The present draft of that change has #if-ery to turn duplication of > column or row names, in QTest data tables, at Qt 7, into a fatal error. > How realistic do folk think it is that client code authors will respond > to the warnings in time for that ? > > I have, for now, included #if-ery complications that let you, when > building QtTestLib, define Q_TEST_REJECT_DUPLICATE_ROW to 0 or 1 in the > build system (and likewise for ..._COLUMN) to override the default > behaviour (0 means warning only even for Qt 7; 1 means fatal even before > Qt 7) but without any build infrastructure (yet) to set that. Is this > adequate or overkill; does anyone have a better suggestion ?
We can flip the default in Qt 7 and also make it a test option that QTEST_MAIN picks up on for code that is too much effort to fix. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development