public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: gcc@gcc.gnu.org
Cc: Mark Mitchell <mark@codesourcery.com>,
	 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: Tue, 21 Sep 2004 08:28:00 -0000	[thread overview]
Message-ID: <414FD78C.5010706@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0409202243230.25608@digraph.polyomino.org.uk>

> The name pedwarn() has been a bit confusing (because it suggests a link to 
> -pedantic which isn't really there, the link being that -pedantic-errors 
> turns pedwarns from warnings to errors), but I don't have a good 
> suggestion for a less confusing name.

-pedantic-errors is itself not very well named... maybe -Wextra-errors 
or something like that would be more suited now that -W has become -Wextra.

Paolo

WARNING: multiple messages have this Message-ID
From: Paolo Bonzini <bonzini@gnu.org>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: Mark Mitchell <mark@codesourcery.com>,
	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: Tue, 21 Sep 2004 08:43:00 -0000	[thread overview]
Message-ID: <414FD78C.5010706@gnu.org> (raw)
Message-ID: <20040921084300.YOicuGPzhBhRP1TzrM7Dz-TZf-K1RIHB1gATjAaGpX4@z> (raw)
In-Reply-To: <Pine.LNX.4.61.0409202243230.25608@digraph.polyomino.org.uk>

> The name pedwarn() has been a bit confusing (because it suggests a link to 
> -pedantic which isn't really there, the link being that -pedantic-errors 
> turns pedwarns from warnings to errors), but I don't have a good 
> suggestion for a less confusing name.

-pedantic-errors is itself not very well named... maybe -Wextra-errors 
or something like that would be more suited now that -W has become -Wextra.

Paolo

  reply	other threads:[~2004-09-21  7:21 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 [this message]
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=414FD78C.5010706@gnu.org \
    --to=bonzini@gnu.org \
    --cc=dalej@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=mark@codesourcery.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).