[Development] Qt 5 types under consideration for deprecation / removal in Qt 6

Giuseppe D'Angelo giuseppe.dangelo at kdab.com
Mon Jun 10 12:13:30 CEST 2019

On 09/06/2019 13:38, André Pönitz wrote:
> So effectively, application developers need to support multiple versions
> of Qt as they cannot really be sure which of their version the
> distributors will combine with which version of Qt which is
> conveniently ignored by our deprecators when they deprecated things
> without offering a reasonably usable alternative.

Isn't it pretty much mandatory, when deprecating something, to also 
state the alternative (in the docs, in the deprecation warnings, etc.)?

How do deprecations change anything here? Isn't enough to state that 
your software requires a given minimum version, and that's it?

(If the deprecation macros are the problem, that's an implementation 
detail of those macros, hopefully fixed now.)

My 2 c,
Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4329 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.qt-project.org/pipermail/development/attachments/20190610/a68d3667/attachment.bin>

More information about the Development mailing list