On Sat, Oct 29, 2011 at 10:58 PM, Manuel Gamito <[email protected]> wrote: > When I compile oiio with both Visual Studio 2008 and 2010 I get > compilation warning galore. These are very likely harmless but in my > own code I always try to remove warnings as they sometimes point to > bugs that would otherwise go unnoticed (besides being an eyesore when > one is trying to get a clean build).
I agree, it's excellent practice to make sure the build happens without a warning. > I'm curious as to what is the approach of oiio to this. Is it that > compilation warnings are simply ignored because trying to remove them > for one platform might create new warnings in a different one? The reason is just that most OIIO development happens with gcc (and perhaps clang?), so nobody has been sufficiently bothered by the msvc warnings to fix them. Let's face it, fixing warnings on a compiler you don't use (or worse, don't even have access to) is a pretty unglamorous passtime ;-) I'm sure patches to fix the various msvc warnings would be welcome. ~Chris _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
