Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!topaz!bentley!kwh
From: kwh@bentley.UUCP (KW Heuer)
Newsgroups: net.lang.c
Subject: Re:  questions from using lint
Message-ID: <798@bentley.UUCP>
Date: Thu, 8-May-86 23:04:31 EDT
Article-I.D.: bentley.798
Posted: Thu May  8 23:04:31 1986
Date-Received: Sun, 11-May-86 02:15:28 EDT
References: <592@brl-smoke.ARPA>
Organization: AT&T Bell Laboratories, Liberty Corner
Lines: 16

In article <592@brl-smoke.ARPA> gwyn@BRL.ARPA (VLD/VMB) writes:
>> 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, the errors detected are not COMPILER errors but CODING errors.
>Second, [examples of other languages]
>Third, "lint"ing is not necessary on every compilation.
>Fourth, on small systems ... [it's better than] complicated multi-pass.
>Fifth, "lint" is rather portable, [but cc] is inherently machine-dependent.

Moreover, because lint is an optional pass which doesn't produce code, it's
safe for it to be overly conservative and flag "errors" which might be okay.
For example, the "possible pointer alignment problem" which results from any
nontrivial cast of malloc().

Karl W. Z. Heuer (ihnp4!bentley!kwh), The Walking Lint