From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: Zack Weinberg <zack@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: [RFC] __extension__ and warnings
Date: Wed, 11 Dec 2002 23:58:00 -0000 [thread overview]
Message-ID: <m3bs3rk851.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20021212065514.GA9823@daikokuya.co.uk>
Neil Booth <neil@daikokuya.co.uk> writes:
| Neil Booth wrote:-
|
| > > I'm now imagining turning the DT_* enumeration into a set of bitflags,
| > > so that you could write e.g.
| > >
| > > diagnostic (DT_EXTENSION | DT_MANDATED | DT_WARNING, "...")
| > >
| > > to achieve the effect of 'pedwarn but shut up under __extension__.'
|
| I think you mean DL_ constants, like I'm using in cpplib? It was meant
| to stand for diagnostic level.
|
| > I prefer this. Fancy changing all error(), warning(), pedwarn(), ...,
| > calls? 8-)
|
| Roughly there are 1965 error(), 820 warning() and 330 pedwarn() calls;
| this includes the _with variants. Piece of cake 8-)
|
| This is probably a good 3.4 project; it would be a great cleanup of our
| diagnostics system. Do you agree Gaby?
Yes, definitely.
-- Gaby
prev parent reply other threads:[~2002-12-12 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 14:16 Neil Booth
2002-12-11 14:19 ` Gabriel Dos Reis
2002-12-11 22:55 ` Mark Mitchell
2002-12-11 15:17 ` Zack Weinberg
2002-12-11 15:54 ` Neil Booth
2002-12-11 23:54 ` Neil Booth
2002-12-11 23:58 ` Gabriel Dos Reis [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=m3bs3rk851.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=neil@daikokuya.co.uk \
--cc=zack@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).