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.dang...@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
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
