This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] trigraphs

From: Neil Booth <neil at daikokuya dot co dot uk>
To: Matt Austern <austern at apple dot com>
Cc: Jason Merrill <jason at redhat dot com>, Devang Patel <dpatel at apple dot com>,gcc-patches at gcc dot gnu dot org
Date: Mon, 21 Jul 2003 22:22:50 +0100
Subject: Re: [PATCH] trigraphs
References: <D4079AA0-BBA5-11D7-A43D-000393A91CAA@apple.com> <wvld6g31z6i.fsf@prospero.boston.redhat.com> <157F22CD-BBB4-11D7-9FDB-00039390D9E0@apple.com> <20030721204502.GJ22306@daikokuya.co.uk> <20093F20-BBC1-11D7-9FDB-00039390D9E0@apple.com>

Matt Austern wrote:-

>   t2.c:1:49: warning: trigraph ??! ignored
> Notice that we're getting this warning even without -Wall.
> 
> You're almost right in thinking that this only happens in string 
> literals.
> The other place it comes up is in multicharacter constants.
> Unfortunately, '????' is a useful placeholder constant in certain kinds
> of MacOS programming.

I now remember that we had a PR about -Wtrigraph being the default earlier
this year, which was argued at length.  The conclusion was that warning
is good if it can change the meaning of a program.  So this decision is
deliberate, and not unreasonable IMO.

If you don't like it, please just quote the 2nd question mark, or
disable it in Apple's GCC.  This debate will go on forever otherwise.

Neil.

References:
- [PATCH] trigraphs
  - From: Devang Patel
- Re: [PATCH] trigraphs
  - From: Jason Merrill
- Re: [PATCH] trigraphs
  - From: Matt Austern
- Re: [PATCH] trigraphs
  - From: Neil Booth
- Re: [PATCH] trigraphs
  - From: Matt Austern

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]