🚀 go-pugleaf

Heigh ho,

I know approximately what the current C standard says about this, and 
I've heard that there is upcoming updates to the standard, which address 
this issue. However, what I want to know is that what is "compiler 
vendors' standard" on this. I've noted that

In most 16bit architectures, ints are 16bit, longs are 32bit.
In most 32bit architectures, ints are 32bit, longs are 32bit.

Well, I don't care about 16bit systems, but what puzzles me is 32bit vs. 
64bit. You see, I thought that in 64bit systems ints would be 64bit and 
longs 64bit. However, when I tried this with gcc running on an Alpha 
machine, it turned out that ints are 32bit and longs are 64bit(of course, 
pointers are also 64bit).

As I use Win32 API compatible types on all platforms, thought that when I 
really want exactly 32bit I could use DWORD and when I want the 
biggest/fastest integer I could use UINT. Of course, on ix86 platform 
DWORD and UINT are equally fast, but as far as I know, on Alpha 
machines(and most other 64bit architectures too) using anything but 64bit 
ints is a bad thing. So, if I continued using UINT, it wouldn't be 
optimal on 64bit architectures - I could use DWORD as well.

Well, I wrote my own types.h to address this issue, but I'd like to know 
about conventions... Is it really so that in most 64bit architectures 
ints are 32bit and longs are 64bit?


Thanks in advance!

--
Hannu "Azure" Koivisto | Saga microkernel, Prophet sub-system OS etc.
Prime Productions      | developer. Software R&D + music.
---------------------------------------------------------------------
What you see is all you get. -Brian Kernigham