public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Koning <pkoning@equallogic.com>
To: gdr@integrable-solutions.net
Cc: neil@daikokuya.co.uk, gcc@gcc.gnu.org
Subject: Re: Warning for trigraphs in comment?
Date: Mon, 19 May 2003 13:22:00 -0000	[thread overview]
Message-ID: <16072.55751.300819.237661@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <m3n0hjxwgo.fsf@uniton.integrable-solutions.net>

>>>>> "Gabriel" == Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
 >> The patch is not appropriate for 3.3.  
 >> The real fix is to remove trigraphs from the standard.

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

I like the notion too.  Trigraphs are an utter misfeature.  

Would it make sense to have the lexer ignore trigraphs (i.e., just
treat ??/ as three characters) unless specifically enabled with
-fenable-trigraphs?   In the unlikely case that anyone actually uses
trigraphs, this would enable them to continue doing so.

   paul

  reply	other threads:[~2003-05-19 13:20 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
2003-05-19 13:22     ` Paul Koning [this message]
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=16072.55751.300819.237661@pkoning.dev.equallogic.com \
    --to=pkoning@equallogic.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --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).