Please note this pending PR: https://github.com/OpenImageIO/oiio/pull/1513
I'm not sure precisely when I'll merge this into master, but it's probably in the next few days, unless somebody makes an impassioned and convincing plea that we should delay. To recap: the master (in-development 1.8) is imminently going to require a minimum of C++11 (which implies gcc >= 4.8 and MSVS >= 2013, or is it 2015?). In the immediate aftermath, it should still be possible to build OIIO with C++11 and call it from apps that are C++03, but I expect that also to break once any C++11 idioms make their way into the public APIs. To put this in perspective, please note that the "11" in C++11 means the year 2011, which to most of us is quite certainly in the past of our current spacetime coordinates. So is 2014, when C++14 became the current standard, and here in late 2016, the spec for C++17 is very nearly complete and the major compilers are rapidly adding support for the parts that are locked down. So the change to a minimum standard to C++11 is not exactly a radical move. Nevertheless, I expect some people to be all "holy crap, my studio/app/dog is not ready for C++11!" And that's ok, because the newly released stable production branch of OIIO, 1.7, is now and will continue to be able to compile with C++03. So as long as you can survive on what's in 1.7 today (and whatever fixes and enhancements we can safely backport), you've probably got until late 2017 before we really, truly stop supporting a release that can work with C++03. But master (1.8) will continue to push forward, and over time you will increasingly covet the new stuff that will never be backported to 1.7. You have been warned. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
