From: Mark Mitchell <mark@codesourcery.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Neil Booth <neil@daikokuya.co.uk>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] __extension__ and warnings
Date: Wed, 11 Dec 2002 22:55:00 -0000 [thread overview]
Message-ID: <49870000.1039673803@warlock.codesourcery.com> (raw)
In-Reply-To: <m31y4okxzz.fsf@uniton.integrable-solutions.net>
--On Wednesday, December 11, 2002 11:10:40 PM +0100 Gabriel Dos Reis
<gdr@integrable-solutions.net> wrote:
> Neil Booth <neil@daikokuya.co.uk> writes:
>
> [...]
>
> | I propose a simpler solution: simply do not emit any pedwarns whilst
> inside | the code affected by __extension__. This is easy to implement
> inside | pedwarn() itself.
> |
> | With this, I can clear up some confused and confusing warning logic,
> and fix | its interaction with cpplib's number interpreter. Thoughts?
>
> At first sight, I would say that sounds reasonable. I reserve my
> comments for the concrete patch.
It sounds plausible to me as well.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-12-12 6:19 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 [this message]
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
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=49870000.1039673803@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=neil@daikokuya.co.uk \
/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).