From: Jason Merrill <jason@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: "Ian Lance Taylor" <iant@google.com>,
"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Ismail Dönmez" <ismail@pardus.org.tr>,
gcc@gcc.gnu.org
Subject: Re: Changes in C++ FE regarding pedwarns to be errors are harmful
Date: Fri, 11 Jan 2008 17:06:00 -0000 [thread overview]
Message-ID: <4787A0F5.9050904@redhat.com> (raw)
In-Reply-To: <4785238C.20302@codesourcery.com>
Mark Mitchell wrote:
> I think Jason's input would be helpful. I remember having a discussion
> about this years ago (1998?), but I don't remember the complete
> rationale. I think the idea was that we wanted many of these things
> (ugly old ARM-era C++ things) to be errors, but didn't want to make it
> impossible to compile old code. They're not "pedantic" in the sense
> that you only care if you're trying extremely hard to be ISO-conformant;
> they're things no sane C++ programmer would do at this point, but we
> want to support for legacy C++ code.
Right. -fpermissive was a kludgey way to make these things errors by
default but still allow them to compile.
> I don't see any a priori problem with changing to match the C front end.
> We could of course change some of the pedwarns into errors if we really
> think they ought to be errors. Or, some of them could be ordinary
> warnings when not -pedantic, and pedwarns when -pedantic.
Sounds like we want a separate category of diagnostic with the current
C++ pedwarn semantics so that we can change pedwarns themselves back to
a warning by default.
Jason
next prev parent reply other threads:[~2008-01-11 17:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 21:27 Ismail Dönmez
2008-01-08 21:34 ` Joe Buck
2008-01-08 21:43 ` Richard Guenther
2008-01-08 21:44 ` Ismail Dönmez
2008-01-08 22:13 ` Andrew Pinski
2008-01-08 22:29 ` Manuel López-Ibáñez
2008-01-08 22:36 ` Ismail Dönmez
2008-01-08 22:45 ` Andrew Pinski
2008-01-09 14:10 ` Paolo Bonzini
2008-01-09 15:38 ` Manuel López-Ibáñez
2008-01-09 15:57 ` Paolo Bonzini
2008-01-08 22:51 ` Manuel López-Ibáñez
2008-01-08 23:02 ` Ismail Dönmez
2008-01-09 1:23 ` Ismail Dönmez
2008-01-09 2:25 ` Manuel López-Ibáñez
2008-01-09 16:47 ` Ian Lance Taylor
2008-01-09 18:11 ` Benjamin Kosnik
2008-01-09 18:18 ` Andrew Pinski
2008-01-09 18:21 ` Paolo Carlini
2008-01-09 19:42 ` Mark Mitchell
2008-01-11 17:06 ` Jason Merrill [this message]
2008-01-11 17:12 ` Joe Buck
2008-01-11 17:55 ` Mark Mitchell
2008-01-12 19:07 ` Jonathan Wakely
2008-01-12 19:50 ` Manuel López-Ibáñez
2008-01-13 3:28 ` Jonathan Wakely
2008-01-13 15:30 ` Manuel López-Ibáñez
2008-01-13 22:56 ` Jonathan Wakely
2008-01-14 2:04 ` Jonathan Wakely
2008-01-14 2:19 ` Manuel López-Ibáñez
2008-01-13 15:33 ` Gabriel Dos Reis
2008-01-13 15:36 ` Ismail Dönmez
2008-01-13 16:09 ` Andreas Schwab
2008-01-13 16:10 ` Ismail Dönmez
2008-01-13 16:13 ` Richard Guenther
2008-01-13 16:41 ` Ismail Dönmez
2008-01-13 23:08 ` Manuel López-Ibáñez
2008-01-14 11:03 ` Paolo Bonzini
2008-01-14 16:23 ` Ismail Dönmez
2008-01-13 16:43 ` Gabriel Dos Reis
2008-01-13 16:45 ` Ismail Dönmez
2008-01-13 19:17 ` Gabriel Dos Reis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4787A0F5.9050904@redhat.com \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=ismail@pardus.org.tr \
--cc=lopezibanez@gmail.com \
--cc=mark@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).