Clang/LLVM 3.4 is scheduled to be released soon, and the release candidate is packaged in Debian Unstable. I took Widelands for a spin, and while the 3.4 release doesn't seem to spot any additional warnings, we have some which should be looked into/fixed. Most of them concerns the same entity which are declared as structs and classes in different places of the code. (I noticed this a while back and since I knew we wanted to use classes throughout I worked a bit on branch for it. Unfortunately it fails to compile due to default private accesibility in classes and I wasn't really comfortable setting _everything_ to public as that might not have been the original intention. So someone else should probably look at that.)
Since bug 913369 was closed once we became warning-free, I've filed a separate bug for the ones which have been added since then.
Clang/LLVM 3.4 is scheduled to be released soon, and the release candidate is packaged in Debian Unstable. I took Widelands for a spin, and while the 3.4 release doesn't seem to spot any additional warnings, we have some which should be looked into/fixed. Most of them concerns the same entity which are declared as structs and classes in different places of the code. (I noticed this a while back and since I knew we wanted to use classes throughout I worked a bit on branch for it. Unfortunately it fails to compile due to default private accesibility in classes and I wasn't really comfortable setting _everything_ to public as that might not have been the original intention. So someone else should probably look at that.)
Since bug 913369 was closed once we became warning-free, I've filed a separate bug for the ones which have been added since then.