From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: "Jonathan Wakely" <jwakely.gcc@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Changes in C++ FE regarding pedwarns to be errors are harmful
Date: Sun, 13 Jan 2008 15:30:00 -0000 [thread overview]
Message-ID: <6c33472e0801121928q22765e54ga1707b45e6a6d7a6@mail.gmail.com> (raw)
In-Reply-To: <4348dea50801121150n52b4f03elde14009d6b6a7a43@mail.gmail.com>
On 12/01/2008, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 12/01/2008, Manuel López-Ibáñez <lopezibanez@gmail.com> wrote:
> >
> > Here is an initial patch implementing some of your proposals. I used
> > pederror as the name of the function. That is, it is an error unless
> > fpermissive is given.
>
> These errors should be independent of -pedantic* unless the if
> (pedantic) check is also present in the code, but that's a special
> case. Have I understood the intention correctly?
Actually, I didn't understand that we wanted to separate fpermissive
and pedantic-errors completely. (Notice that the internal
declaration/definition of fpermissive actually mentions pedantic.) But
I agree with you: they should be unrelated.
> I don't really like the name permerror either though, relaxable_error
> is accurate but not great either.
I actually like permerror better than the alternative
permissive_error. I think those two are the only ones that make sense.
> Thanks for doing this - I agree with your other decisions about what
> should be a pedward or a pederror/whatever in e.g. lex.c and parser.c
Your information above was very helpful. But I am still not sure about
the rest of pedwarns.
Cheers,
Manuel.
next prev parent reply other threads:[~2008-01-13 3:28 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
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 [this message]
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=6c33472e0801121928q22765e54ga1707b45e6a6d7a6@mail.gmail.com \
--to=lopezibanez@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).