In our previous episode, J?rgen Hestermann said:
> Because of these weak definition of types (which is very confusing IMO)
> I often use a check in the implementation part of units if I have to
> reliy on sizes:
>
> if sizeof(Word)<>2then Halt(9000);
> if sizeof(DWord)<>4 then Halt(9001);
"The cardinal type is currently always mapped to the longword type.
The definition of the cardinal and integer types may change from one
architecture to another and from one compiler mode to another."
"Always" or "may change" ? :-?
Current always, but may change ? Perfect English. Now so, but not
In our previous episode, JoshyFun said:
> MvdV> Afaik most is in the docs, but some short pointers:
>
> Sure :) but as I said not found :( and the information I had found
> does not describe the 32/64 bits differences.
First, if you don't know the 64-bit memory model discussions have a look
here:
Hello Marco,
Saturday, January 10, 2009, 12:36:37 AM, you wrote:
MvdV> Afaik most is in the docs, but some short pointers:
Sure :) but as I said not found :( and the information I had found
does not describe the 32/64 bits differences.
MvdV> 32 64
MvdV>
In our previous episode, JoshyFun said:
> Can anybody help me understanding the variables which will be
> different (in size) in 32 and 64 bits versions, and which ones are
> "size fixed" across platform bits ?
>
> So the question, something like a table:
Afaik most is in the docs, but some short
Hello FPC-Pascal,
Can anybody help me understanding the variables which will be
different (in size) in 32 and 64 bits versions, and which ones are
"size fixed" across platform bits ?
So the question, something like a table:
32 64
unsigned 16 bits WO