public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/10613: Please make -Wtrigraphs the default Date: Sun, 04 May 2003 21:36:00 -0000 [thread overview] Message-ID: <20030504213600.31703.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/10613; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: Zack Weinberg <zack@codesourcery.com> Cc: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: preprocessor/10613: Please make -Wtrigraphs the default Date: Sun, 4 May 2003 22:33:20 +0100 Zack Weinberg wrote:- > > This option is in effect unless trigraphs are turned on, and is > > implied by @option{-Wall}. With the exception of a trigraph that > > would form an escaped newline, warnings are not given for trigraphs > > within comments as they do not affect the meaning of the program. > > is confusing. I would say instead > > Most trigraphs in comments cannot affect the meaning of the program. > However, a trigraph that would form an escaped newline (@samp{??/} > at the end of a line) can, by changing where the comment begins or > ends. Therefore, only trigraphs that would form escaped newlines > produce warnings inside a comment. > > This option is implied by @option{-Wall}. If @option{-Wall} is not > given, this option is still enabled unless trigraphs are enabled. > To get trigraph conversion without warnings, but get the other > @option{-Wall} warnings, use @samp{-trigraphs -Wall -Wno-trigraphs}. That's great, thanks, I'll plagiarise in full. Neil.
next reply other threads:[~2003-05-04 21:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-04 21:36 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-04 20:56 Zack Weinberg 2003-05-04 20:06 Neil Booth 2003-05-04 20:05 neil 2003-05-04 10:06 Neil Booth 2003-05-04 10:06 Hallvard B Furuseth 2003-05-04 9:40 neil 2003-05-04 1:16 Zack Weinberg 2003-05-03 23:26 Neil Booth 2003-05-03 23:16 Hallvard B Furuseth
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=20030504213600.31703.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).