home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!uunet.ca!canrem!dosgate!dosgate![peter.curran@canrem.com]
- From: "peter curran" <peter.curran@canrem.com>
- Subject: Re: Questions about token merging and trigraphs
- Message-ID: <199220.4396.29952@dosgate>
- Reply-To: "peter curran" <peter.curran@canrem.com>
- Organization: Canada Remote Systems
- Distribution: comp
- Date: 20 Dec 92 08:51:55 EST
- Lines: 33
-
-
- kdq@quest.UUCP (Kevin D. Quitt) writes (in part) ...
-
- KD> I believe I've shown that your first adjective is incorrect,
- KD>and your second is questionable. As to harm, no code was broken;
- KD>the only thing that changed was the appearance of some output -
- KD>and you've yourself indicated that is of no great harm.
-
- That is not true - as Dr. Andrews showed (an no doubt others could),
- some code was broken. Whether the damage to the code was serious
- or not, no one but the authors and users of that code can determine.
- Certainly, as several people have pointed out, the problem is
- easily fixed, *once the cause is understood*. That is the hard part,
- since many people have never heard of trigraphs.
-
- However, the question that the committee had to face was, does the
- benefit of trigraphs outway the costs. They decided, correctly IMHO,
- that it does. I believe that ISO could never have accepted the C
- standard without them (or something similar). That would have
- meant that ISO would have produced a modified standard, and once
- modifications had started, there is no telling where they would
- have stopped. We would have ended up with one standard for the US,
- and a second, perhaps substantially different one, everywhere else.
- The cost of that would have far exceed the cost of fixing a few
- programs broken by trigraphs.
-
- Peter Curran
- Usenet: peter.curran@canrem.com RIME: CRS (#118)
- ---
- ■ DeLuxe² 1.25 #12339 ■
- --
- Canada Remote Systems - Toronto, Ontario
- World's Largest PCBOARD System - 416-629-7000/629-7044
-