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: <4422@haddock.ISC.COM> Date: 6 Jun 88 16:57:57 GMT References: <5215@ico.ISC.COM> <1490@eneevax.UUCP> <1988May23.000451.751@utzoo.uucp> <5391@ico.ISC.COM> <8805261740.AA00659@explorer.dgp.toronto.edu> Reply-To: karl@haddock.ima.isc.com (Karl Heuer) Organization: Interactive Systems, Boston Lines: 10 In article <8805261740.AA00659@explorer.dgp.toronto.edu> flaps@dgp.toronto.edu (Alan J Rosenthal) writes: >In other words, a useful compiler will not implement trigraphs but will >give a warning message when it encounters them. If it issues warning messages, why should the compiler bother to implement the old meaning? I'd think that the set of users who have programs containing accidental trigraphs *and* can look at a compiler warning without wanting to make it go away (by fixing their programs) would be very small. Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint