[Development] On deprecating functions

Thiago Macieira thiago.macieira at intel.com
Mon Mar 4 19:28:22 CET 2019

On Monday, 4 March 2019 09:58:40 PST Edward Welbourne wrote:
> Christian Ehrlicher (4 March 2019 17:51) wrote
> > So what's the correct way to deprecate a function and not forgetting
> > about QT_DEPRECATED later on as it happened with a lot of functions
> > during Qt4 times?
> Isn't that what
> is for ?

The point raised by hjk is that this causes warnings to anyone compiling code 
that needs to retain compatibility. There's no grace period. This is probably 
why we only documented the functions were deprecated with \obsolete, but never 
enabled warnings (except for Qt4-compat things). In that scheme, finding 
deprecated functions is done by raising QT_DEPRECATED_SINCE in your 
buildsystem and see what fails, instead of having warnings printed at you.

Should we go back to this?

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products

More information about the Development mailing list