On quarta-feira, 4 de setembro de 2013 23:37:50, Thiago Macieira wrote: > Deprecation warnings are not errors. They are left as warnings. > > Besides, how is this different from a change in a library causing a > compiler error? There have been several of those due to reliance on > indirect includes, for example. > > Also, new compiler updates can break existing code if our code was bad. > We're using C++11 before all compilers implement everything, so it's quite > possible that better implementations cause existing code to break.
Can we please give the feature a try, for a week or two, with -warnings-are- errors enabled in all CI builds? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
