Path: utzoo!attcan!uunet!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: trigraphs in X3J11
Message-ID: <8002@brl-smoke.ARPA>
Date: 1 Jun 88 14:05:34 GMT
References: <4314@haddock.ISC.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <4314@haddock.ISC.COM> karl@haddock.ima.isc.com (Karl Heuer) writes:
>However, some external representation of this character has to exist anyway.
>After all, I can do putc('#', outf) to a text stream and read it back in,
...
>Rebuttal, anyone?

How can it be rebutted?  It's exactly correct, and is why I think
trigraphs were unnecessary in the first place.

Note: the code might be written "putc('??=', outf)" but it's still
a distinct character represented in the proposed C standard by the
glyph "#".  Sites that want to import strictly conforming programs
have to be able to handle non-trigraph sources anyway.  Trigraphs
are a (poor) solution to the wrong problem.