diff options
| author | Frédéric Brière <fbriere@fbriere.net> | 2020-08-23 11:47:59 -0400 |
|---|---|---|
| committer | Frédéric Brière <fbriere@fbriere.net> | 2020-08-23 12:33:23 -0400 |
| commit | 1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb (patch) | |
| tree | 38409f3d62fe208459301f0dbf3b359f452db1cc /THANKS | |
| parent | 0944e02eb0eca17c58cc9775fff37d41165d16fb (diff) | |
| download | twinkle-1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb.tar twinkle-1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb.tar.gz twinkle-1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb.tar.lz twinkle-1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb.tar.xz twinkle-1ad8560c9b97af9e4d80d21d6e45c3c4cd4dc2fb.zip | |
Suppress deprecation warnings from Qt
Starting from Qt 5.13, QT_DEPRECATED_WARNINGS is now enabled by default.
Unfortunately, methods are often deprecated not long after a suitable
alternative is available, meaning that getting rid of these warnings
would require breaking backwards compatibility (or sprinkling QT_VERSION
checks everywhere).
(See QList::fromStdList() as an example, which was marked as deprecated
merely a month after range constructors were made available.)
This reverts things to how they were before. Getting rid of these
warnings will probably be part of the job when porting to Qt 6.
Diffstat (limited to 'THANKS')
0 files changed, 0 insertions, 0 deletions