This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] -Wc++0x-compat


"Manuel López-Ibáñez" <lopezibanez@gmail.com> writes:

| > > Could you please add OPT_cxx0x-compat to the warning statement so
| > > that -Werror=c++0x-compat works?
| >
| > Oh, sure. I hadn't realized what that first parameter to "warning"
| > actually meant :)
| 
| I am not sure whether the correct one is OPT_Wcxx0x_compat or
| OPT_Wc__0x_compat.

  OPT_Wc__0x_compat

See the output of the automatically generated header out of c.opt.

| You cant test which one works just using
| -fdiagnostics-show-option, this should print the option that generated
| that warning. If it doesn't print -Wc++0x-compat, then you got it
| wrong. (Or also using  -Werror=c++0x-compat as suggested).
| 
| > Given that it takes more than a decade to get a new revision of the
| > C++ standard out, I don't expect we'll end up with all that many -W
| > switches. Isn't what we have good enough?
| >
| 
| I hope GCC will last for another two decades but yes. We can add
| -Wcompat=* or -Wstd-compat=* in 2020. That is actually a good
| argument. :-)

Please be aware that if you introduce redundancies you have to check
consistency.  If you make the system orthogonal, you just need to
compose.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]