This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: warning: trigraph ... ignored
- To: Nix <nix at esperi dot demon dot co dot uk>
- Subject: Re: warning: trigraph ... ignored
- From: Zack Weinberg <zack at wolery dot cumb dot org>
- Date: Tue, 13 Jun 2000 18:14:50 -0700
- Cc: dl8bcu at gmx dot net, gcc at gcc dot gnu dot org
- References: <20000613223216.A12898@Marvin.DL8BCU.ampr.org> <87bt15du13.fsf@loki.wkstn.nix>
On Wed, Jun 14, 2000 at 12:46:00AM +0100, Nix wrote:
> Thorsten Kranzkowski <th@Marvin.DL8BCU.ampr.org> writes:
>
> > /usr/src/linux-2.4.0-test1-ac18-work/include/linux/delay.h:19:44: warning: trigraph ??/ ignored
> >
> > The relevant part of delay.h (linenumbers added):
> >
> > 19 * specific values can be defined in asm-???/delay.h as an override.
> >
> > I don't exactly know what trigraphs are, I assume some weird replacement
> > expression for unusual characters. But I don't think gcc should warn about
> > them in _comments_ !
>
[snip excellent explanation]
All that you say is true - but I want to add that there is no good
reason for us to warn about trigraphs inside comments that don't
affect where it starts or ends. E.g. if you write
/* asm-???/delay.h */
the program has the same meaning whether or not the trigraph is
converted. We still warn about that because the part of cpp that does
trigraph conversion doesn't know anything about comments.
This is fixed in the "new lexer", due Real Soon Now.
zw