> if the two of them don't decide to add their own proprietary "extensions" to the language. icc has always had its own dialect of C++, which in practice means

> if the two of them don't decide to add their own proprietary "extensions" to the language. icc has always had its own dialect of C++, which in practice means that there is "C++" code that only compiles on icc but is rejected by clang++ and g++. With Intel switching to the clang frontend, I would hope that their interpretation of C++ will become more, not less, standard conform.