cppcheck would be nice, but only without failing the builds - the 3 memory leaks cited above are false positives. We'd have to completely redesign the memory handling in the Panel class to get rid of those warnings. Since it has proven to work fine across many years, I am very reluctant to invest development time into that one, because we have more important fish to fry.
I would love to get the full cppcheck as clean as reasonably possible though, because there is good potential for catching some bugs there. -- https://code.launchpad.net/~widelands-dev/widelands/codecheck/+merge/326647 Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands/codecheck into lp:widelands. _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : widelands-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
