🚀 go-pugleaf

     I just bought Gimple Software's Lint and I'm using it with Aztec C.
I've come across some problems.  First off, the include file "functions.h"
and library definition file, "manx.l" that came with Lint didn't agree on 
about 30 of the functions return value types.  I used the disk based update
of the RKM for 1.2 to correct them.  It turned out that manx.l agreed with
the RKM, and functions.h didn't.  functions.h declared the return types to
be shorts when the RKM claimed they were long or BOOL.  That was easy
enough to fix, but it took some time.

     My current problem is with InitBitMap().  I've been compiling with
+l because I was too scared about getting the arguments wrong; but now
that I have Lint to tell me when my arguments are wrong, I decided to
do things right.  When I ran a program I've been working on through Lint,
it told me that the arguments I was passing to InitBitMap() were shorts
instead of longs, which manx.l claims they should be.  Just to be sure,
I looked InitBitMap up in the disk based RKM, it said that depth is a
BYTE, and width and height are SHORT.
     Which is correct?  manx.l or the RKM?  When I was compiling with +L
it didn't matter because everything gets type cast to a 32 bit int when
they're passed to functions.  But if I compile without the +L, the wrong
type will cause all kinds of Hell.

     I realize that they could both be right; Aztec's library stubs might
require longs even though the library function might only need BYTEs and
SHORTs, but I just want to make sure.


Other than the few minor, fixable problems I've had, I really like Lint.
Its kind of slow, but it already caught an error (other than the argument
types) that got by the compiler.


Thanks for any help.
Rich Champeaux
Clemson University