The basic problem with the feature defines is that nobody is maintaining them. There are also way too many of them to be able to test all combinations, so things are bound to break.
Currently I'm more leaning towards advocating that people do feature selection based on the modules (shared libs) they include rather than feature defines. Cheers, Lars On 12/12/11 10:21 PM, "ext Stephen Kelly" <[email protected]> wrote: > >Hi there, > >Is there any plan to keep or remove the defines in features.txt in Qt 5? >(eg, QT_NO_SQL, QT_NO_DATESTRING etc) > >A colleague told me about talk of removing all the ifdefs, but he thought >he'd convinced whoever it was he was talking to that the stuff should be >kept. > >Is it something that would need to be modularised? > >Thanks, > >-- >Stephen Kelly <[email protected]> | Software Engineer >KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company >www.kdab.com || Germany +49-30-521325470 || 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 _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
