> I think it is better we mention it (in the manual) and its deprecation plan How to get the current GCC manual http://gcc.gnu.org/onlinedocs/gcc/Standards.html#Standards fixed to include this information (c++0x deprecation)? Before fixing we need to know when we will be deprecating c++0x? Regards, Kannan -----Original Message----- From: Mailaripillai, Kannan Jeganathan (STSD) Sent: Tuesday, April 24, 2012 11:28 AM To: gcc-help@xxxxxxxxxxx Subject: RE: redundant option to select c++ dialect options in 4.7.0? > What does it hurt? I was going through 4.7.0 GCC manual. Under section "2.2 C++ language" there was no mention of "c++0x" though it is accepted by the compiler. I think it is better we mention it (in the manual) and its deprecation plan in the future release to avoid surprise to the end user of the compiler. Regards, Kannan -----Original Message----- From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx] On Behalf Of Marc Glisse Sent: Tuesday, April 24, 2012 11:10 AM To: Mailaripillai, Kannan Jeganathan (STSD) Cc: gcc-help@xxxxxxxxxxx Subject: Re: redundant option to select c++ dialect options in 4.7.0? On Tue, 24 Apr 2012, Mailaripillai, Kannan Jeganathan (STSD) wrote: > Hi, > > We have -std=c++0x and -std=c++11 options recognized by 4.7.0 compiler. > Do we really need to accept (going forward) -std=c++0x when we have > -std=c++11 option to select the c++11 standard? Yes, for a few releases, for backward compatibility. What does it hurt? -- Marc Glisse
