I wrote:
>> TL;DR: there's a new [[Deprecation]] wiki page, please review.
Friedemann Kleint (1 August 2022 09:49) replied:
> It misses an important part, IMO:
> Try to get an idea of the impact of your planned deprecation by building
> all of Qt and ideally Qt Creator (producing patches fixing t
Hi,
> TL;DR: there's a new [[Deprecation]] wiki page, please review.
It misses an important part, IMO:
Try to get an idea of the impact of your planned deprecation by building
all of Qt and ideally Qt Creator (producing patches fixing the
deprecation warnings).
If that turns into an huge ex
From: Development on behalf of Edward
Welbourne
Sent: Thursday, July 21, 2022 11:13 AM
To: Lars Knoll
Cc: Qt development mailing list
Subject: Re: [Development] How to do deprecation
On 20 Jul 2022, at 16:50, Edward Welbourne wrote:
>> We noticed recently that
On 20 Jul 2022, at 16:50, Edward Welbourne wrote:
>> We noticed recently that some APIs had been wrapped in #if-ery on
>> QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or one
>> of the QT_DEPRECATED_VERSION* macros prepended to the actual
>> declarations within that #if-ery. This
Hi Eddy,
On 20 Jul 2022, at 16:50, Edward Welbourne
mailto:edward.welbou...@qt.io>> wrote:
Hi all,
TL;DR: there's a new [[Deprecation]] wiki page, please review.
We noticed recently that some APIs had been wrapped in #if-ery on
QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or
Hi all,
TL;DR: there's a new [[Deprecation]] wiki page, please review.
We noticed recently that some APIs had been wrapped in #if-ery on
QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or one of
the QT_DEPRECATED_VERSION* macros prepended to the actual declarations
within that #if-
