On 24/11/2020 16:29, Edward Welbourne wrote:
I'm guessing you meant generic / special. I'm more keen on keeping
everything deprecated, but with a special macro. (Or maybe just bump
the deprecation version to 6.0 instead of 5.15?)
I think changing the version to 6.0 is a sane option.  It'll leave it
visibly deprecated, it'll let someone defining the right macro [*] enable
that deprecation, but it won't inflict deprecation warnings on those who
just want to build with 5.15.

[*] IIUC, that'd be: -DQT_DISABLE_DEPRECATED_BEFORE=0x060001

Then, should it actually be deprecated as 5.255? So asking for 6.0.*0* deprecations would flag it.

Thanks,

--
Giuseppe D'Angelo | [email protected] | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to