Xref: utzoo comp.lang.c:19566 comp.unix.questions:14477
Newsgroups: comp.lang.c,comp.unix.questions
Path: utzoo!utgpu!jarvis.csri.toronto.edu!dgp.toronto.edu!flaps
From: flaps@dgp.toronto.edu (Alan J Rosenthal)
Subject: misleading type names (was: Re: lint won't verify printf formatting...)
Message-ID: <1989Jun24.151636.6997@jarvis.csri.toronto.edu>
Organization: Dynamic Graphics Project, University of Toronto
References: <328@tree.UUCP>


In article <328@tree.UUCP> stever@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).