Path: utzoo!utgpu!water!watmath!clyde!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: trigraphs in X3J11
Message-ID: <4147@haddock.ISC.COM>
Date: 23 May 88 20:17:50 GMT
References: <5215@ico.ISC.COM> <1490@eneevax.UUCP> <1988May23.000451.751@utzoo.uucp>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 18

In article <1988May23.000451.751@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>>[It should be controlled by an option flag]
>I would expect that this is the way many C compilers will implement trigraphs;
>I know of some that already take that approach.  Lots of people share your
>view that trigraphs are ugly.

I countersuggest that the compiler should always recognize trigraphs, and
issue a warning message if any are encountered.  Then add an option to supress
this warning.

This way, the compiler would still be conforming, and in the unlikely event
that some of my code uses a string containing two question marks followed by
one of the magic characters, I'd find out about it.

(This is based on the assumption that trigraphs stay in.  I'd prefer that they
be removed, but in any case I don't expect them to get in my way.)

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint