From: Marc Espie <espie@quatramaran.ens.fr>
To: gcc@gcc.gnu.org
Subject: Re: PATCH: work-around for bug in -traditional-cpp
Date: Sun, 07 Dec 2003 18:30:00 -0000 [thread overview]
Message-ID: <200312071822.hB7IMu703669@quatramaran.ens.fr> (raw)
In-Reply-To: <bqb9lu$m85$2@clipper.ens.fr>
In article <bqb9lu$m85$2@clipper.ens.fr> you write:
>On Sat, Nov 29, 2003 at 09:50:42PM +0000, Neil Booth wrote:
>> >
>> > Okay, it looks like trad-cpp is messing with skipping.
>>
>> If you're skipping you shouldn't even be attempting to expand
>> macros.
>
>Yes, sure. But I don't think trad-cpp knows whether it's skipping
>at this point. It does expand macros early, and then it will use
>them or discard them when it finds out whether it's skipping or not.
>
>This is not my code. I'm only concerned about not getting warnings
>when I should not get any, e.g., make the code work.
>
>If you can figure what's actually going on, and can clean it up,
>that will be fine.
>
Okay, is anybody actually intending to look deeper at this code ?
The work-around I posted actually fixes things for me, and if no-one
wants to search at what's going on deeper, I believe that a preprocessor
without bogus warnings is better than a preprocessor with bogus warnings...
next parent reply other threads:[~2003-12-07 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bqb9lu$m85$2@clipper.ens.fr>
2003-12-07 18:30 ` Marc Espie [this message]
2003-11-25 15:31 Bug in traditional cpp in gcc 3.3.2 ? Marc Espie
2003-11-25 17:01 ` Andreas Schwab
2003-11-29 18:14 ` PATCH: work-around for bug in -traditional-cpp Marc Espie
2003-11-29 23:11 ` Neil Booth
2003-11-29 23:52 ` Marc Espie
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=200312071822.hB7IMu703669@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
/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).