public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> 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 01:16:00 -0000 [thread overview] Message-ID: <20030504011601.3801.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/10613; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.co.uk> Cc: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/10613: Please make -Wtrigraphs the default Date: Sat, 03 May 2003 18:13:57 -0700 Neil Booth <neil@daikokuya.co.uk> writes: > Hallvard B Furuseth wrote:- > >> Gcc *silently* compiles code like `puts("??!")' incorrectly: It >> prints `??!' instead of `|'. I agree that not converting >> trigraphs is the best default, they are most likely programmer >> errors. However, fixing a programmer error without telling the >> programmer is very bad, we'll test our code and think it's >> correct when it will misbehave with other (correct) compilers. > > That would be OK with me. What do you think, Zack? There's always > -Wno-trigraphs for those who don't want it. This is one of a *lot* of warnings that GCC issues only at -Wall, which indicate a bug with >90% confidence. So I don't think there is anything wrong with the status quo; however, I would not object to enabling this warning by default. We could do it experimentally in 3.4 and see how many people complain. The suggested documentation change is a good idea. zw
next reply other threads:[~2003-05-04 1:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-04 1:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-04 21:36 Neil Booth 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 Hallvard B Furuseth 2003-05-04 10:06 Neil Booth 2003-05-04 9:40 neil 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=20030504011601.3801.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --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).