home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!srhqla!quest!kdq
- From: kdq@quest.UUCP (Kevin D. Quitt)
- Newsgroups: comp.lang.c
- Subject: Re: Questions about token merging and trigraphs
- Message-ID: <iJqwVB1w165w@quest.UUCP>
- Date: Wed, 16 Dec 92 19:36:29 PST
- References: <1TA04E3@cdis-1.compu.com>
- Reply-To: srhqla!quest!kdq
- Organization: Job quest (805) 251-8210, So Cal: (800) 400-8210
- Lines: 33
-
- tanner@cdis-1.compu.com (Dr. T. Andrews) writes:
-
- > ) What are trigraphs?
- > Trigraphs are an unpleasant invention from the successor to the
- > horse committee...
-
- Perhaps Dr. Andrews should spend a little time in thought before
- lashing out at necessary and occasionally useful, if obscure, parts of C.
-
-
- > Trigraphs are a nasty way to write certain characters in the C
- > source character set. These more difficult characters are
- > represented as three characters starting with "??". For
- > instance, you can represent `#' as "??=".
-
- Trigraphs are the *only* way to represent certain critical
- characters on machines that do not support the ASCII character set.
- Their use on other machines is supported for portability.
-
-
- > The change means that certain old programs may have strings, most
- > likely error messages, compiled into something unexpected.
-
- I suppose anything is possible, but it's pretty remote. Just how
- remote it is, is easily shown by the fact that many experienced C
- programmers know nothing about trigraphs; therefore they've never had a
- problem from them. The cost of something unexpected in an error string
- is a fairly small price to pay for allowing non-ASCII machines to
- support portable C code; after all, *code* isn't going to break.
-
-
- _
- Kevin D. Quitt 96.37% of all statistics are made up. srhqla!quest!kdq
-