On Wed, Dec 25, 2013 at 7:19 PM, Luca Risolia <luca.riso...@linux-projects.org> wrote: > > I would like to propose the adoption of C++11 to my colleagues for our > production code. > > We use to rebuild everything with the same compiler version each time (GCC > 4.7.3 for now), so ABI incompatibilities between different GCC versions are > not > an issue for us. However, with C++11 in mind everything would have to be > rebuilt with the "-std=c++11" compiler flag turned on, as we could not accept > any possible binary incompatibilities between C++11 and C++98. > > I have been personally using almost all the supported C++11 compiler features > for long time without any particular problems. I am also aware of the fact > that some big companies already decided to switch from C++98 to C++11 > entirely. However, some of my colleagues might not be familiar with C++11 at > all and might wonder what the claim "experimental support for C++11" from the > official GCC >4.7.3 status pages means in terms of "risks" for our code. > > Apart from some (minor) C++11 features not being implemented in the standard > library or in the compiler yet, I'd like to know what else intrinsic to C++11 > with GCC we should consider before switching.
Questions like this should go to gcc-h...@gcc.gnu.org rather than gcc@gcc.gnu.org, which is a developer list. Please take any followups to gcc-help. Thanks. The major work on GCC 4.7 was completed before the C++11 standard was finalized, so it more or less had to be considered experimental. There were no substantial revisions in later versions of GCC, except for adding new features required by the standard. I don't think there are any substantial risks due to the experimental label of the C++11 support in GCC 4.7. Of course support for the new C++11 features was new and as such more likely to have bugs, though of course known bugs were fixed by the current 4.7.3 release. You'll have to judge for yourself how much of that sort of risk you want to tolerate. Hope this helps. Ian
