This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: New macro expander preamble
- To: Zack Weinberg <zackw at Stanford dot EDU>
- Subject: Re: New macro expander preamble
- From: Neil Booth <neilb at earthling dot net>
- Date: Sat, 18 Nov 2000 12:10:46 +0000
- Cc: gcc-patches at gcc dot gnu dot org
- References: <20001025231849.A20348@daikokuya.demon.co.uk> <20001026165546.D24137@wolery.stanford.edu> <20001026202325.H24137@wolery.stanford.edu> <20001027194118.B13589@daikokuya.demon.co.uk> <20001030203249.R8628@wolery.stanford.edu> <20001117000415.A20787@daikokuya.demon.co.uk> <20001116164730.C18114@wolery.stanford.edu>
Zack Weinberg wrote:-
> > The double warning is caused because parse_identifier handles the '?'
> > (it might be an escaped newline) as well as _cpp_lex_token for the
> > next token; in other words it's handled twice. It's not restricted
> > to stdin - any file works too, so we can put it in the testsuite.
> >
> > I can't see a clean way to fix this just yet; but it's on my list.
>
> Maybe have parse_identifier emit the warning only for ??/ and only
> when converted? Otherwise, we know _cpp_lex_token will get it. This
> might speed up the exit path from p_i, too.
Zack,
I've had a good look at this bug; surprisingly it's quite subtle. I
can't see an easy way to get it right in all cases - identifiers,
numbers, second character of a token etc. etc.
This is low priority, but it is on my list. I'll come back to it
later.
Neil.