[Development] QT_DEPRECATED_SINCE and QT_DISABLE_DEPRECATED_BEFORE

[Thiago Macieira]

On Tuesday, 1 de November de 2011 10:55:49 Frans Klaver wrote:
> On Tue, Nov 1, 2011 at 10:43 AM, Thiago Macieira <thiago at kde.org> wrote:
> > One more thing: QT_DEPRECATED expands to empty during the Qt build.
> > 
> > Should we enable QT_DEPRECATED_WARNINGS?
> 
> FWIW, my personal experience is that build warnings are noticed before
> documentation changes. I always feel a deprecation warning during the
> build is more likely to push people to move to the new API than just
> changing the documentation -- a lot of people like warning-free
> builds.
> 
> So I'd say that would be a yes.

I'd also like to work on enabling -Werror, but usually deprecation warnings 
cannot be avoided, so I'll add also a Wno-error-deprecated.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20111101/ec3439bb/attachment.sig>