-
Ivan
From: Development on behalf of Jaroslaw
Kobus via Development
Sent: Thursday, November 14, 2024 9:05 AM
To: development@qt-project.org; Alex Blasche
Subject: Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt
Would it be possible to turn on warnings for de
: Thursday, November 14, 2024 8:52 AM
To: development@qt-project.org
Subject: Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt
Hi,
Let's move forward with the given patch. Patch discussion seems to have mostly
settled with only marginal (if any) improvement discussions.
Once
36
To: development@qt-project.org
Subject: Re: [Development] Deprecated vs deprecated-to-be-removed APIs in Qt
Am 24.10.24 um 16:32 schrieb Ivan Solovev via Development:
Hi,
following up on the Deprecation vs Compatibility discussion from
the Qt Contributor Summit [0], I implemented a macro that allo
Hi,
following up on the Deprecation vs Compatibility discussion from
the Qt Contributor Summit [0], I implemented a macro that allows to mark
the APIs as deprecated and to-be-removed in the Next Major Release [1].
[0]: https://wiki.qt.io/QtCS2024_Deprecate
[1]: https://codereview.qt-project.org/
Am 24.10.24 um 16:32 schrieb Ivan Solovev via Development:
Hi,
following up on the Deprecation vs Compatibility discussion from
the Qt Contributor Summit [0], I implemented a macro that allows to mark
the APIs as deprecated and to-be-removed in the Next Major Release [1].
[0]:https://wiki.qt.io
Ivan Solovev (24 October 2024 16:32) wrote:
> 3. New names
>
> While looking through the sources, I noticed that many of the APIs
> simply got renamed. We have a lot of such cases for Qt 6.0, for
> example in QFuture-related APIs.
>
> Another typical example here is the renaming of the error() sign
