the gcc website still says: "gcc's support c++11 still experimental." (http://gcc.gnu.org/projects/cxx0x.html). feel hesitant arguing within organization press move c++11 features while people releasing compiler this. should argue "-std=c++11" if gcc says experimental?
i suspect 1 of things can argue until rare happens (cows coming home, hell freezing, etc) , not find resolution.
the key here "experimental support" means if on support contract gcc, can't raise "defect" ticket against 11 features. on other hand, can expect features robust, have been discussed long time before c++11 specification came out.
the key determine if product correctly built compiler still rely on testing of product code (both units @ various levels (functions, classes, shared libraries, exectutables makes sense product) , "complete" product). doesn't change based on whether c++11 support experimental or not. non-experimental code breaks @ times in compilers.
the other part @ of course "what benefit get, , how risk influence project". changing entire system, or small part in 1 corner, if breaks worked around doing more steps in different way?
in end, it's have go "what's best balance between moving forward , avoiding risk".
Comments
Post a Comment