Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!sharkey!cfctech!teemc!ka3ovk!ki4pv!cdis-1!tanner
From: tanner@cdis-1.uucp (Dr. T. Andrews)
Newsgroups: comp.unix.xenix
Subject: Re: comp.unix.xenix
Keywords: cc error messages in SCO UNIX System V/386 r3.2
Message-ID: <7759@cdis-1.uucp>
Date: 28 Nov 89 16:42:55 GMT
References: <529@s5.Morgan.COM> <69@van-bc.UUCP> <71@van-bc.UUCP>
Organization: CDI-DLD
Lines: 17

It is said...
) "Beware of compilers which correct errors".

This is reasonable advice.  I don't want the thing to continue and
actually compile/link a program which has errors, even to the extent
of swallowing
	printf("blunge") printf("more blunge")	/* missing ';' */

On the other hand, I'd sure prefer that to the cascade of errors
which results from certain omissions.  Missing punctuation can
generate incredible error cascades using SCO's version of the
Microsoft compiler.  A heuristic which, on error, attempted in
some order the insertion of ')', '}', and ';' might be a welcome
diagnostic tool for that "first attempt to compile".
-- 
Mulroney: "Cut trains.  Drive in | {bpa,uunet}!cdin-1!cdis-1!tanner
Canada.  We need the acid rain." | {attctc gatech!uflorida}!ki4pv!cdis-1!tanner