We are aiming to branch and release OIIO 1.5 before the end of the year, with the same old language and compiler requirements we have always had. We have strived thus far to continue being compatible with gcc 4.1 (and, I think, MSVC 9?, something fairly old).
In case you are not aware of it, http://www.vfxplatform.com/ On Linux, the major VFX vendors and studios are all planning to upgrade their gcc floor from 4.1 to 4.8 for anything released in 2015 (though, alas, not full C++11 until possibly the next year). I've been coveting a lot of the new C++ features -- auto, move semantics, initializer lists, lambdas, range-based 'for', and so on. This page has a handy chart of compiler versions versus new C++ features: http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport It looks to me like a rather nice batch of features allowed by gcc 4.8 should also be supported by clang >= 3.1 and MSVC >= 11.0 (I think that's Visual Studio 2012). So, the particular question to contemplate over the next few weeks: * For new development in 2015 and beyond (OIIO >= 1.6), is there anybody who would still have a reasonable requirement for gcc < 4.8, MSVC < 11.0, or clang < 3.1? Keep in mind that we would continue to have available and support OIIO 1.5 that only needs gcc4.1/msvc9.0, and as well that being incompatible with gcc >= 4.8 will probably also make you incompatible with next year's Maya, Houdini, Nuke, and so on. My current inclination is to wrap up OIIO 1.5 release with the current C++ feature set we've been using, but then starting in January allow new development to use some additional C++ features. Exactly which features is TBD, and will depend on what the new "floor" is that we decide for the compiler versions on the major platforms. Suggestions and feedback appreciated. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
