On Thursday, 27 de October de 2011 07:23:58 Thiago Macieira wrote: > On Wednesday, 26 de October de 2011 23.28.53, Olivier Goffart wrote: > > After a small talk with David Faure, we came to the conclusion that maybe > > it would be a good temporary solution to define > > QT_DISABLE_DEPRECATED_BEFORE to 4.9 to re-enable (temporarely) all the > > deprecated function, untill the feature freeze. So others module have time > > to adapt to the deprecation warnings. > > > > The change is there: http://codereview.qt-project.org/#change,7494 > > > > Comments? > > Qt itself needs to be built with that macro enabled. On some platforms > (*cough* Windows *cough*), the compiler (*cough* MSVC *cough*) will try to > export the entire class, including inline functions, so it needs to see all > functions.
One more thing: QT_DEPRECATED expands to empty during the Qt build.
Should we enable QT_DEPRECATED_WARNINGS?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
