🚀 go-pugleaf

    Are the type-checking capabilities of gcc with ANSI any substitute for
    lint?  I noticed that many parameter differences we're ignored using
    gcc, and caught with lint.

The ANSI C typechecking capabilities are a substitute for lint, but only
if you use them.  If you declare a function prototype, then all calls 
convert the arguments to the expected type, or report errors when 
arguments cannot be converted.

However, passing a character where a float is expected is not an error,
because the conversion is possible.

In ANSI C, enum types are abbreviations for standard integral types,
and enum values are actually integers.  So you won't get an error if
the function "asks for" an enum type and the actual argument is an
integer.  This case normally does not even require conversion.

In order to make your program compilable using traditional C, I suggest
keeping the function definitions in traditional form, and adding a
separate prototype declaration inside of #ifdef __STDC__.

Keep in mind when doing this that if the traditional function definition
declares an argument of type char or short, the prototype must say int;
if the function definition declares an argument of type float, the
prototype must say double.  This is also part of the ANSI standard.