Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!umn-cs!zuhn
From: zuhn@umn-cs.cs.umn.edu (Zoo)
Newsgroups: comp.lang.c
Subject: Re: Can lint help an ANSI-C programmer?
Message-ID: <ZUHN.90Jun2145646@umn-cs.cs.umn.edu>
Date: 2 Jun 90 18:56:46 GMT
References: <6328.265D8157@puddle.fidonet.org> <1754@tkou02.enet.dec.com>
	<009377E6.C32DAB80@rigel.efd.lth.se> <3118@goanna.cs.rmit.oz.au>
Sender: news@cs.umn.edu (News administrator)
Organization: Univ. Of Minnesota Computer Science Department
Lines: 19
In-Reply-To: ok@goanna.cs.rmit.oz.au's message of 31 May 90 11:25:42 GMT

>>>>> On 31 May 90 11:25:42 GMT, ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe) said:

Richard> How is an ANSI C compiler, with just one file to look at,
Richard> going to notice that you've defined two functions with the
Richard> same name in different files?  Yes, the linker will catch
Richard> that one, but the linker won't tell you which lines the
Richard> definitions are on, and lint will. 

Then fix your linker... I use GNU ld and it does just what you say
the linker won't do.  You don't need lint to catch this.


I use GNU CC (writing ANSI style programs) and would like to be able to
use lint but I don't have access to any that deal with ANSI'isms.  But
the rest of the compile-link suite of tools is getting better and better
in respect to catching things that were once caught only by lint.

david d [zoo] zuhn		Univ. of Minnesota Dept. of Astronomy
zoo@aps1.spa.umn.edu		Automated Plate Scanner	Project