>> General warning-id's: >> >> * ALL >> * DEFAULT >> * LEVEL<N> > >And `NONE`.
I'm less interested in all warnings and more interested in a clear level that is the highest warning level that does not provide false positives is. After setting the warning level precisely, the next step is setting warnings as errors. There might be cases where the compiler can come up with warnings that are useful, but should sometimes be ignored without changing code or adding pragmas. Also, I don't know how often warnings are added to various compilers. It may be a moving target. Geoff Viola This message contains confidential information and is intended only for the recipient. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
