Don't panic. From these responses, it's clear that we can't really make much use of C++11 features for a while, too many people are stuck on old compilers.
I should have clarified that I'm talking strictly about OIIO internals -- for link compatibility with apps that must use older compilers, I was not really considering using any newfangled things in the public APIs. In theory, anyway, all gcc's >= 4.1 (I think) should be mutually linkable as long as you stick to 4.1 compatible stuff in the public APIs. But there may be corner cases, so it's probably best to be extra conservative since I have no good way to test the full cross-product of compilers versus every DCC app that we care about. Pete Black said: "Default compiler on OS X Snow Leopard is gcc 4.2, I compile OIIO on my mac laptop and would ideally like to continue doing so." Me, too, although these days I run clang 3.3 on my OS 10.6 laptop, and it works great and I've had no compatibility issues with gcc (though I do not use -stdlib to use their new standard library, which is NOT compatible with gcc). Clang is vastly superior in both compilation speed as well as understandable error messages, compared to gcc. Also, it's pretty close to the bleeding edge of C++11 (and now C++14) feature adoption. On Aug 27, 2013, at 5:40 PM, Larry Gritz wrote: > I won't hold you to this. And I'm not planning any immediate changes. But > thinking about where we are going with toolchain dependencies, coding > standards, and how conservative we need to be about newer C++ features... > > Think ahead to where you or your facility will likely be in, say, January > 2014. > > * What C++ compiler and version do you think will be the oldest (i.e., least > C++11-compliant) you'll need OIIO to support? > > * What Boost version do you think will be the oldest you'll need OIIO to > support? > > * Can you think of any other dependencies (OpenEXR, etc.) that you are likely > to need support for any versions MORE THAN TWO YEARS OLD, i.e., dating from > 2011 or earlier? > > If you aren't comfortable answering on the mail list, a private email to me > is fine, and I will summarize results later. > > For simplicity, you need not reply if you are already using this year's > tools: GCC >= 4.8, MSVC >= 11 (VS 2012), Clang >= 3.3. > > > -- > Larry Gritz > [email protected] > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
