Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!archone!byron
From: byron@archone.tamu.edu (Byron Rakitzis)
Newsgroups: comp.lang.c
Subject: Re: lint (was: Funny mistake)
Message-ID: <13627@helios.TAMU.EDU>
Date: 22 Mar 91 14:39:20 GMT
References: <1991Mar22.055335.23091@athena.mit.edu> <13619@helios.TAMU.EDU> <5036@goanna.cs.rmit.oz.au>
Sender: usenet@helios.TAMU.EDU
Organization: College of Architecture, Texas A&M University.
Lines: 9

In article <5036@goanna.cs.rmit.oz.au> ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe) writes:
>
>But will your hand-holding compiler check that a *group* of files are
>consistent?  That's what I really depend on lint for.

I don't see what you need over and above good function-prototype checking.
I am going to write a compiler strongly biased towards ANSI C; if you don't
supply prototypes, you will pay the price of not having the use of
unprototyped functions checked for type safety.