public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@stanford.edu>
To: Michael Meissner <meissner@cygnus.com>
Cc: Aparna Ranish <aparna_ranish@rediffmail.com>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: trigraphs ????
Date: Thu, 05 Jul 2001 10:45:00 -0000	[thread overview]
Message-ID: <20010705104508.C1926@stanford.edu> (raw)
In-Reply-To: <20010705123957.B13188@cse.cygnus.com>

On Thu, Jul 05, 2001 at 12:39:57PM -0400, Michael Meissner wrote:
> On Thu, Jul 05, 2001 at 07:15:53AM -0000, Aparna  Ranish wrote:
> > Hi
> > Can somebody tell me what is the usage of trigraphs ??? Is it supported by
> > all the Compilers.
> 
> It is required to be supported by all ISO standard compilers.  The
> usage of trigraphs is to work around problems where some characters
> in the C source character set aren't available in the local
> character set (ie, some varients of ISO 646 in other countries use
> the same byte value for curley braces and other characters).

However, note that trigraphs are disabled by default in GNU C/C++/ObjC.
To enable them, you must use a command line switch: any of -trigraphs,
-ansi, -std=c89, -std=c99, -std=c++98 will do the trick.  The latter
four have other effects as well.

-- 
zw   You have to care about the 'fair trial' part; you have to care about
     the 'due process of law' part, and you have to care about these things
     *more* than you care about putting child molestors away.
     	-- Graydon Saunders

  reply	other threads:[~2001-07-05 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  0:10 Aparna  Ranish
2001-07-05  9:40 ` Michael Meissner
2001-07-05 10:45   ` Zack Weinberg [this message]
2001-07-05  7:59 Yann Collete
2001-07-05  9:47 ` Ingo Krabbe

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=20010705104508.C1926@stanford.edu \
    --to=zackw@stanford.edu \
    --cc=aparna_ranish@rediffmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=meissner@cygnus.com \
    /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).