From: Mark Mitchell <mark@codesourcery.com>
To: Matt Austern <austern@apple.com>
Cc: gcc@gcc.gnu.org, Dale Johannesen <dalej@apple.com>,
Nathan Sidwell <nathan@codesourcery.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: DR handling for C++
Date: Mon, 20 Sep 2004 21:08:00 -0000 [thread overview]
Message-ID: <414F44E0.90506@codesourcery.com> (raw)
In-Reply-To: <4FFC8911-0B47-11D9-ADB7-000A95AA5E5E@apple.com>
Matt Austern wrote:
> Isn't the fundamental problem that we're using pedwarns differently in
> the C and C++ front ends? In the C front end you don't even see
> pedwarns unless you use a special compiler flag, and making them into
> errors requires an even more special compiler flag. It's very odd
> that it means something so different in the C++ front end.
>
> This is really going off into a different subject (pedwarn policy, not
> DR policy), but I'd suggest that we:
> 1. Change the C++ front end's pedwarn defaults to match the C front
> end's policy.
> 2. Remove -fpermissive, which #1 will render redundant.
> 3. Go through our pedwarns and decide which ones should be errors,
> which ones should be warnings, and which ones really should just be
> pedwarns.
Yes, that's exactly what I was trying to suggest.
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com
next prev parent reply other threads:[~2004-09-20 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 20:44 Mark Mitchell
2004-09-20 20:47 ` Dale Johannesen
2004-09-20 20:55 ` Andrew Pinski
2004-09-20 21:26 ` Dale Johannesen
2004-09-20 21:00 ` Mark Mitchell
2004-09-20 21:04 ` Matt Austern
2004-09-20 21:08 ` Mark Mitchell [this message]
2004-09-20 21:36 ` Gabriel Dos Reis
2004-09-20 23:42 ` Joseph S. Myers
2004-09-21 8:28 ` Paolo Bonzini
2004-09-21 8:43 ` Paolo Bonzini
2004-09-21 12:39 ` Joseph S. Myers
2004-09-20 20:54 ` Gabriel Dos Reis
2004-09-20 21:01 ` Mark Mitchell
2004-09-20 21:07 ` Gabriel Dos Reis
2004-09-20 21:14 ` Mark Mitchell
2004-09-20 21:41 ` Matt Austern
2004-09-20 22:32 ` Gabriel Dos Reis
2004-09-20 22:59 ` Mark Mitchell
2004-09-20 23:12 ` Matt Austern
2004-09-20 23:16 ` Mark Mitchell
2004-10-18 9:19 ` Jason Merrill
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=414F44E0.90506@codesourcery.com \
--to=mark@codesourcery.com \
--cc=austern@apple.com \
--cc=dalej@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@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).