From: Jason Merrill <jason@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, Matt Austern <matt@lafstern.org>,
Nathan Sidwell <nathan@codesourcery.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: DR handling for C++
Date: Mon, 18 Oct 2004 09:19:00 -0000 [thread overview]
Message-ID: <xypwtxr2uxh.fsf@miranda.boston.redhat.com> (raw)
In-Reply-To: <414F37E0.3020509@codesourcery.com> (Mark Mitchell's message of "Mon, 20 Sep 2004 13:04:48 -0700")
On Mon, 20 Sep 2004 13:04:48 -0700, Mark Mitchell <mark@codesourcery.com> wrote:
> I think that part of the confusion here comes from the
> -pedwarn/-fpermissive situation. I think -fpermissive should just be
> removed. I think that many of our pedwarns should become errors, many
> should become warnings, -pedantic-errors should be off by default.
-fpermissive was a compromise between the desire for stricter conformance
checking and the desire for backwards compatibility with users' code, so
that users would be able to use newer compiler versions while they update
their code. I still feel strongly that this is an important goal, but I'm
open to other ideas about how to implement it.
Jason
prev parent reply other threads:[~2004-10-18 4:48 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
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 [this message]
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=xypwtxr2uxh.fsf@miranda.boston.redhat.com \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=matt@lafstern.org \
--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).