From: Neil Booth <neil@daikokuya.co.uk>
To: Joe Buck <jbuck@synopsys.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Paul Koning <pkoning@equallogic.com>,
zack@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: Warning for trigraphs in comment?
Date: Mon, 19 May 2003 20:04:00 -0000 [thread overview]
Message-ID: <20030519200046.GC8256@daikokuya.co.uk> (raw)
In-Reply-To: <20030519110505.B6565@synopsys.com>
Joe Buck wrote:-
> On Mon, May 19, 2003 at 04:44:26PM +0200, Gabriel Dos Reis wrote:
> > What is happening with current GCC in production use is that GCC
> > choosed NOT to warn for trigraphs in comment even if -Wtrigraph.
>
> Ideally GCC should not warn about trigraphs in comments, ever, unless that
> trigraph can change the meaning of the program.
That is what 3.4 does. It's not as easy as you might think to do this
efficiently, trigraphs being a PITA efficiency-wise anyway, never mind
doing long-winded checks to see if something constitutes a change in
the meaning of the program.
Basically 3.4 warns about trigraph escaped newlines in comments, even
in the middle of a big block comment, but nothing else.
Neil.
next prev parent reply other threads:[~2003-05-19 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 13:37 Gabriel Dos Reis
2003-05-18 18:54 ` Zack Weinberg
2003-05-18 20:01 ` Neil Booth
2003-05-18 20:14 ` Zack Weinberg
2003-05-19 6:57 ` Gabriel Dos Reis
2003-05-18 19:36 ` Neil Booth
2003-05-19 6:51 ` Gabriel Dos Reis
2003-05-19 13:22 ` Paul Koning
2003-05-19 14:35 ` Zack Weinberg
2003-05-19 14:37 ` Paul Koning
2003-05-19 14:51 ` Gabriel Dos Reis
2003-05-19 14:55 ` Paul Koning
2003-05-19 18:11 ` Joe Buck
2003-05-19 20:04 ` Neil Booth [this message]
2003-05-19 15:10 ` Zack Weinberg
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=20030519200046.GC8256@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=jbuck@synopsys.com \
--cc=pkoning@equallogic.com \
--cc=zack@codesourcery.com \
/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).