Path: utzoo!attcan!uunet!n3dmc!johnl
From: johnl@n3dmc.UUCP (John Limpert)
Newsgroups: comp.lang.c
Subject: Re: trigraphs in X3J11
Message-ID: <343@n3dmc.UUCP>
Date: 26 May 88 03:37:52 GMT
References: <5215@ico.ISC.COM> <7937@brl-smoke.ARPA> <5424@ico.ISC.COM>
Reply-To: johnl@n3dmc.UUCP (John Limpert)
Organization: N3DMC, Silver Spring, Maryland
Lines: 14


I think a simple solution to this problem is possible.  Why not
have the compiler print a warning if it detects a trigraph?
This would reduce the chances of breaking a program when it was
recompiled with an ANSI C compiler.  If the warning was only
printed the first time a trigraph was encountered, it wouldn't
be too annoying.  Restricting the check to literal strings might
be worthwhile.  Many compilers print warnings about constructs
that are legal, but are often unintentional coding errors.

-- 
John A. Limpert
UUCP:	johnl@n3dmc.UUCP	uunet!n3dmc!johnl
PACKET:	n3dmc@n3dmc.ampr.org	n3dmc@wa3pxx