misleading type names (was: Re: lint won't verify printf formatting...)

[Alan J Rosenthal]

In article <328 at tree.UUCP> stever at tree.UUCP (Steve Rudek) writes:
>After wrestling with variable overflow for a while, I figured the "good enough"
>solution would be to just change most int definitions to INT and #define
>INT as long.

Why not use "long" to mean long, or at the very least use "LONG" or "int32"??
Defining INT as long is asking for trouble (unless it's an entry in the
obfuscated C contest).