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 10:06:00 -0000	[thread overview]
Message-ID: <20030504100603.22001.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: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/10613: Please make -Wtrigraphs the default
Date: Sun, 4 May 2003 10:59:02 +0100

 Hallvard B Furuseth wrote:-
 
 > No.  -Wall would be enough if -trigraphs was turned on by default, or if
 > trigrahs where syntax errors by default.  My problem is that code
 > _silently_ compiles differently on gcc with standard options and on an
 > ISO C compiler.  This is very different from normal gcc extensions,
 > where the code won't compile at all on an ISO C compilers - then one
 > certainly notices the difference.
 
 OK, I'll prepare a patch for 3.4 where -Wtrigraphs is on by default.
 However, if there are complaints I will revert it to -Wall only, since
 that is the long-standing behaviour.
 
 Neil.


             reply	other threads:[~2003-05-04 10:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 10:06 Neil Booth [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  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=20030504100603.22001.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: 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).