public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ingo Krabbe <ikrabbe@earthling.net>
To: Yann Collete <collette@clt13bi.der.edf.fr>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: trigraphs ????
Date: Thu, 05 Jul 2001 09:47:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0107051847430.12939-100000@flathead.burg.de> (raw)
In-Reply-To: <200107051459.QAA11904@clphr01.der.edf.fr>

>
> Is trigraphs used for something ????
>
I think they have been used for something but are not very usefull in our
days. Trigrpahs should achieve extending some charactersets which don't
have some characters. Anyway there has to be some reason why ISO once has
introduced these sequences.

Excerpt from gcc manual:
=================================== snip
       -trigraphs
           Process ISO standard trigraph sequences.  These are
           three-character sequences, all starting with ??, that
           are defined by ISO C to stand for single characters.
           For example, ??/ stands for \, so '??/n' is a charac-
           ter constant for a newline.  By default, GCC ignores
           trigraphs, but in standard-conforming modes it con-
           verts them.  See the -std and -ansi options.

           The nine trigraph sequences are

           ??( -> [

           ??) -> ]

           ??< -> {

           ??> -> }

           ??= -> #

           ??/ -> \

           ??' -> ^

           ??! -> |

           ??- -> ~

           Trigraph support is not popular, so many compilers do
           not implement it properly.  Portable code should not
           rely on trigraphs being either converted or ignored.

=================================== snip

  reply	other threads:[~2001-07-05  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  7:59 Yann Collete
2001-07-05  9:47 ` Ingo Krabbe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-05  0:10 Aparna  Ranish
2001-07-05  9:40 ` Michael Meissner
2001-07-05 10:45   ` 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=Pine.LNX.4.33.0107051847430.12939-100000@flathead.burg.de \
    --to=ikrabbe@earthling.net \
    --cc=collette@clt13bi.der.edf.fr \
    --cc=gcc-help@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).