Thanks for the quick answer, and sorry for posting to the wrong list. In my defense I did google quite a lot and found some people thinking that GCC might switch, and some that it might not. And mainly I was just hopeful, since I was hoping that the ABI compatibility issues with boost in linux package repositories would resolve itself within a few years... One reference from the Debian mailing lists: https://lists.debian.org/debian-devel/2013/08/msg00117.html Anyway, thanks again. And now I'll have to go and reconsider my alternatives of if I can get to use C++11... /Lars On Fri, Jan 24, 2014 at 10:36 AM, <pinskia@xxxxxxxxx> wrote: > > >> On Jan 24, 2014, at 1:26 AM, Marc Glisse <marc.glisse@xxxxxxxx> wrote: >> >> Wrong list, please send any follow-ups to gcc-help@xxxxxxxxxxx only. >> >>> On Fri, 24 Jan 2014, Lars Hagström wrote: >>> >>> I'm wondering whether GCC 4.9 will switch to -std=gnu++11 as default? >> >> No. This is asked regularly, google should find the answer easily. > > Considering GCC has not switched to c99 by default what makes someone think GCC should switch to c++11 by default? > > -- Andrew > >> >>> I got an error that implies that "auto" is not usable, which would >>> mean that C++11 is not enabled, but I also got a warning that implied >>> that gnu++11 is "enabled by default". >>> >>>> error: ‘xdir’ does not name a type >>> >>>> warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default] >>> >>> Or does the "enabled by default" bit mean something other than I think it means? >> >> It is the warning that is enabled by default (in other messages you would see [-Wunused] or [-Wformat] etc to tell you which option controls this warning). >> >> -- >> Marc Glisse
