This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: redundant option to select c++ dialect options in 4.7.0?
Thanks Marc Glisse.
> The flag -std=c++0x is already deprecated, that's why it isn't documented
> anymore...
I understand that option c++0x is mentioned in 4.6.3 manual. It is not
mentioned in 4.7.0 manual. But 4.7.0 compiler accepts the option c++0x
without any warning (saying it is deprecated).
My concern is that anyone moving from 4.6.3 to 4.7.0 will continue to use
c++0x (unless they read the manual). But when we decide (say in 4.8.0) to
remove c++0x from the valid argument list for -std, it will be a surprise
for the end user as he is not notified prior to that (say in 4.7.0, through
the compiler itself).
I do not know the usual procedure (in gcc) followed to
deprecate (stop accepting) any options. I would have followed the procedure:
1. Emit (deprecation) warning for usage of c++0x in 4.7.0 compiler.
2. Have a note (in 4.7.0 manual) about the deprecation of c++0x in upcoming
(say 4.7.2 or 4.8.0) release.
3. Deprecate (stop accepting) the option in future release (say 4.7.2)
Regards,
Kannan
-----Original Message-----
From: Marc Glisse [mailto:marc.glisse@inria.fr]
Sent: Wednesday, April 25, 2012 12:12 PM
To: Mailaripillai, Kannan Jeganathan
Cc: gcc-help@gcc.gnu.org
Subject: RE: redundant option to select c++ dialect options in 4.7.0?
On Wed, 25 Apr 2012, Mailaripillai, Kannan Jeganathan wrote:
>> 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)?
By submitting a patch.
http://gcc.gnu.org/contribute.html
The file is gcc/doc/standards.texi.
> Before fixing we need to know when we will be deprecating c++0x?
The flag -std=c++0x is already deprecated, that's why it isn't
documented anymore...
--
Marc Glisse