Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!ulysses!sfsup!jbu
From: jbu@sfsup.UUCP (+Urban J.)
Newsgroups: comp.unix.xenix
Subject: Re: Create Lint Libraries?
Keywords: lint
Message-ID: <5323@sfsup.UUCP>
Date: 24 May 89 23:37:02 GMT
References: <202@melpar.UUCP> <1989May19.152951.27404@ateng.ateng.com>
Reply-To: jbu@/guest2/jbuUUCP (xt1123-+Urban J.)
Organization: AT&T Information Systems
Lines: 25

In article <1989May19.152951.27404@ateng.ateng.com> chip@ateng.ateng.com (Chip Salzenberg) writes:
>According to toppin@melpar.UUCP (Doug Toppin):
>>I have been trying to create a lint library with

On most UNIX/XENIX boxes lint(1) is just a shell script that calls lint1
and lint2.  You goal in life is to just call lint1.  Look at the source
for lint and you'll get the correct option.

The input file (proto_type.c) should just be a proto type file, e.g. like this:

$ cat proto_type.c
tyee(x, y) int x, y; {return (1);}
char *apples(pear) char *part; {return ("RC");}

Then when you lint it (first pass only), lint will create a proto_type.ln file.
This .ln file can be used by lint2 (second pass lint, that checks for
arguments/return codes, et. al.).

If you want, you can always just suppy the proto_type.c file every time,
this would slow down lint(1) because it would always have to recreate the .ln
guy each time.

Sincerely,

John Urban