Francois Gouget wrote:
> On Thu, 2 Nov 2000, David Elliott wrote:
> [...]
> > Okay, I can understand why not to use windef.h. But I figured if its a hack
> > it might as well really be a hack. I won't use windef.h anymore but will
> > instead typedef int INT; in the MSVCRT header files. I think that is the
> > only definition I wanted anyway.
>
> Why do you use INT? The Microsoft headers use int like any well
> behaved C library header. In particular exit, _exit, and _errno all use
> int.
>
Well, I was thinking that we would want the types to be the same as Win32 and
therefore use INT which could later be defined as a 32-bit integer if int was
64-bit on the platform. I am not really familiar with how different compilers
handle the size of an int. It was my understanding that it's usually the native
int on the processor which would not work very well for binary compatibility.
But maybe I could be wrong in my thinking and I should just go ahead and use int.
-Dave
