public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Warning for trigraphs in comment?
Date: Mon, 19 May 2003 06:51:00 -0000	[thread overview]
Message-ID: <m3n0hjxwgo.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20030518193113.GC13596@daikokuya.co.uk>

Neil Booth <neil@daikokuya.co.uk> writes:

| Gabriel Dos Reis wrote:-
| 
| > is extracted from Herb's GTW #86 -- full message appended below.
| > I would suggest we warn for trigraphs in comments.
| 
| I changed this particular case a few weeks ago.

Thanks!

Since the discussion was about compilers released for production used,
I just content myself with checking 3.2.3 and 3.3 and found that the
comment and the behaviour were indeed there.

| In general I think warning about trigraphs in comments is a bad idea.

I see you stated a personal opinion but I think we need to weight that
against the fact that we got real world experience and the fact that
the comment is not accurate. 

|  This particular
| case I was of course always aware of, but considered it obscure.
| 3.4 documentation and behaviour is already good enough for you I
| think. 

It is not particularly me.  I was reporting input from discussions
which at first sight looked to me as just an academic exercise and it
turned out that it happened in reality.

| The patch is not appropriate for 3.3.
| 
| The real fix is to remove trigraphs from the standard.

Oh, I'm all for removing trigraphs, digraphs, quadrigraphs and
whatevergraphs -- I've also thought they were mistakes.  But, in fact,
I'm skeptical that  would ever happen. 

Anyway, I'm glad to hear that 3.4 will behave differently.

-- Gaby

  reply	other threads:[~2003-05-19  6:49 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 [this message]
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
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=m3n0hjxwgo.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.co.uk \
    /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).