5 ms·
Sun/Oracle was moving to Apache stdcxx to replace their existing awful options of a way out of date Rogue Wave STL or an almost as out of date STLport. https:/
by twoodfin 13y ago
Sun/Oracle was moving to Apache stdcxx to replace their existing awful options of a way out of date Rogue Wave STL or an almost as out of date STLport.
https://forums.oracle.com/thread/2293516 https://forums.oracle.com/thread/2293516
I wonder what they'll do now. The sensible thing would be to adopt clang and libc++, so we can be reasonably certain they won't do that.
- apaprocki 13y agoStudio 13 will use the g++ runtime: http://docs.oracle.com/cd/E37069_01/html/E37071/gndfg.html#OSSWNgnddm http://docs.oracle.com/cd/E37069_01/html/E37071/gndfg.html#O...
- pjmlp 13y agoDoes this mean Oracle will eventually ditch SunPro for GCC?
- apaprocki 13y agoNo, I doubt it. Studio has features that don't exist in GCC/clang and there is a lot of support for older code/systems that make the newer compilers incompatible for some uses. It's just a shortcut to reuse the "easy" reusable part and focus on the compiler.
- pjmlp 13y agoThanks. Last time I used SunPro was in Solaris 2.6 / 7 around 1999-2001, hence my question.
- twoodfin 13y agoNot so bad. I wonder if we'll still have Solaris customers when this compiler is ready for use. Are they planning on shipping this runtime with the OS eventually?
- apaprocki 13y agoYes, they took this approach because otherwise it is a pretty monumental effort to create a C++11 std lib from scratch and they didn't have any work done on the compiler side yet.
- pjmlp 13y agoAh, the joys of doing UNIX development in commercial UNIX systems with the vendors compilers back in 2000.