On sexta-feira, 6 de dezembro de 2013 13:41:34, Olivier Goffart wrote: > There used to be a 'compilerwarnings' autotest that made sure there was no > warning in the headers (in a more strict ways that the warnings we check > while compiling Qt itself). But i think it's gone.
I still have a pending change that compiles each and every public header independently -Werror and defining the keywords. None of my builds with Clang or GCC have any warnings. There are a few with ICC because it's too eager on warning 177 (unused function). I have warnings in MSVC's own headers after we started using <algorithms> more, so I don't bother with MSVC warnings anymore. -- 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
