This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: backslash-newline, trigraphs, and the C standard
- To: geoffk at envy dot cygnus dot com (Geoff Keating)
- Subject: Re: backslash-newline, trigraphs, and the C standard
- From: Joe Buck <jbuck at synopsys dot COM>
- Date: Thu, 13 Jan 2000 12:10:22 -0800 (PST)
- Cc: zack at wolery dot cumb dot org (Zack Weinberg), gcc at gcc dot gnu dot org
> I thought the point of the trigraph warnings is so that when you
> accidentally write a trigraph, use gcc, and then have to port to some
> compiler that has trigraphs on by default, you don't get a nasty shock.
Right. No one will care whether there is a trigraph in a comment if it
doesn't make a difference.
> In that case, aren't trigraphs that would end comments particularly
> interesting?
There is only one case I can find where a trigraph can affect where a
comment ends:
/* some comment ??/*/
With trigraphs on, this is
/* some comment \*/
so the comment is not ended. Can anyone come up with any other cases?
If not, then it seems that the desired behavior would be to suppress
trigraph warnings inside constants except for this one case.