🚀 go-pugleaf

In article <1993Jun4.110115.8333@cas.org> lvirden@cas.org (Larry W. Virden) writes:
>These suggestions are only true if you plan on compiling all the pieces of
>your program together each time you do a compile .  Many folk use libraries,
>and thus find it extremely difficult to get good warnings about arguments
>passed to various functions, etc.

No, gcc can make every check that lint can make if you require that there
be a prototype in an .h file for every library function used.  For this
reason, lint is pretty much going away.

>Lint allows one to build libraries of arguments and return codes for functions
>so as to not have to compile so much at one time.

A lint library looks very much like a prototype and provides no extra
information about a function that a prototype does not provide.  If your
vendor provides a lint library but no prototypes, you can probably convert
the lint library to a set of prototypes.  To make sure that nothing
escapes your notice, use the following gcc switch:

`-Wstrict-prototypes'
     Warn if a function is declared or defined without specifying the
     argument types.  (An old-style function definition is permitted
     without a warning if preceded by a declaration which specifies
     the argument types.)





--
Joe Buck	jbuck@ohm.EECS.Berkeley.EDU