Hi all, Over the last year, several developers have spent time fixing warnings reported by various tools. This sort of maintenance is best done by the original developer at the point of commiting. Warnings are fairly easy to fix and knowing about them improves programming skills.
An easy way to make this happen as a normal part of the Github merge process is to increase the GCC warning level (we use -Wall here at work) and tell gcc to treat warnings as errors. It will then stop at the first warning, and will be visible as a build failure on Github. An obvious prerequisite for this would be to ensure that the current code builds without warnings but this can be sorted out. Thoughts? - Noel ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
