public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/10614: -Wtrigraphs does not catch // ??/
Date: Sun, 04 May 2003 10:26:00 -0000	[thread overview]
Message-ID: <20030504102600.28947.qmail@sources.redhat.com> (raw)

The following reply was made to PR preprocessor/10614; it has been noted by GNATS.

From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: gcc-bugs@gcc.gnu.org,
    Zack Weinberg <zack@codesourcery.com>,
    gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/10614: -Wtrigraphs does not catch // ??/
Date: Sun, 4 May 2003 12:24:20 +0200

 Neil Booth writes:
 > You could persuade me that it's worthwhile warning for ??/ followed by
 > a newline in any kind of comment with -Wtrigraphs.
 
 Sounds good.  As I said in report preprocessor/10613, I think it's
 important to warn about _silent_ changes from ISO C.
 
 I suggest you also warn about ??/ <spaces/tabs> <newline>, since
 gcc ignores these spaces/tabs (with a warning).
 
 > it would warn about ??/ followed by a newline in C block comments that
 > don't change behaviour, but I don't think that would bother those who
 > want trigraph warnings off in comments.
 
 Right.  If it bothers anyone, you could add a comment in the -Wtrigraphs
 doc that ??/<newline> in comments is warned about because it _may_
 change the meaning of the program, and leave it at that.
 
 > Is that an acceptable compromise?
 
 Yes, fine.
 
 -- 
 Hallvard


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 10:26 Hallvard B Furuseth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-04  9:56 Neil Booth
2003-05-04  9:26 Hallvard B Furuseth
2003-05-04  9:05 neil
2003-05-03 23:36 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=20030504102600.28947.qmail@sources.redhat.com \
    --to=h.b.furuseth@usit.uio.no \
    --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).