>>> 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?)
On 24/11/2020 16:29, Edward Welbourne wrote: >> 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 Giuseppe D'Angelo (Tuesday, November 24, 2020 16:40) replied > Then, should it actually be deprecated as 5.255? So asking for 6.0.*0* > deprecations would flag it. Seems reasonable, although 5.31 would suffice. Eddy.
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
