Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!cad!faustus
From: faustus@cad.UUCP (Wayne A. Christopher)
Newsgroups: net.lang.c
Subject: Re: questions from using lint
Message-ID: <287@cad.UUCP>
Date: Tue, 6-May-86 14:08:34 EDT
Article-I.D.: cad.287
Posted: Tue May  6 14:08:34 1986
Date-Received: Thu, 8-May-86 21:42:44 EDT
References: <7097@cca.UUCP> <759@ccird2.UUCP> <475@snow.warwick.UUCP> <256@valid.UUCP>
Organization: U. C. Berkeley CAD Group
Lines: 13

In article <256@valid.UUCP>, gelfand@valid.UUCP writes:

> I have been programming for many years (over 20) in many different 
> languages, and C is the only language that I can remember that
> has a separate program (lint) to find and report compiler errors in 
> source code.

First, lint doesn't report ERRORS -- it reports possible problems.  Second,
there is no other way you can check things like argument types (except for
prototyping, which will make lint much less useful), since you generally 
compile only one .c file at a time.

	Wayne