Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbcad!ames!hao!husc6!bbn!rochester!PT.CS.CMU.EDU!IUS1.CS.CMU.EDU!edw
From: edw@IUS1.CS.CMU.EDU (Eddie Wyatt)
Newsgroups: comp.unix.wizards,comp.unix.questions,comp.lang.c
Subject: Re: "C" Program Verifier
Message-ID: <260@PT.CS.CMU.EDU>
Date: Thu, 29-Oct-87 22:22:11 EST
Article-I.D.: PT.260
Posted: Thu Oct 29 22:22:11 1987
Date-Received: Wed, 4-Nov-87 05:25:25 EST
References: <46@wvucswv.UUCP>
Sender: netnews@PT.CS.CMU.EDU
Distribution: na
Organization: Carnegie-Mellon University, CS/RI
Lines: 38
Keywords: C UNIX Verifier
Xref: mnetor comp.unix.wizards:5210 comp.unix.questions:4723 comp.lang.c:5213

> I am looking for a UNIX utility that can check the calling
> conventions of "C" functions and their parameters even though those
> functions are scattered throughout a number of files.
> Thus the utility would check the usage of functions against their
> definitions even though the usage is in one file and the definition
> is in another file.
> This utility would be similar to "lint".
> However lint only checks functions in a single file, not in multiple files.

You should be able to use lint to check multiple files.  Here's an example
script that I use to check a library I maintain.  You can also get lint
to generate a "lint library" so that others using your code can check
their code against it.


#!/bin/csh -s

lint    -a \
	-x \
	-DDEBUGBB \
        -I../include \
        -I../comsrc\
        -I/usr/include \
        -I/usr/cs/include \
        -I. \
	arrayf.c bbinit.c bbrestf.c globals.c network.c specf.c slistf.c \
	timef.c tokenf.c udtf.c  check.c misc.c fconvert.c \
	tokenqueue.c messagebuffer.c errortraps.c generichashtable.c \
	genericqueue.c missingf.c bindings.c lispfunc.c genid.c \
 	termio.c memalloc.c  token_cache.c ddshow.c geo_obj.c \
	vehicle_motion.c y.tab.c >& err


-- 

					Eddie Wyatt

e-mail: edw@ius1.cs.cmu.edu