> As for Cardinal being only 32bit - that stinks because it's a major
> oversight on my part. Is there a data type equivalent to Cardinal for
> 64-bit? I mean - I tried to use a gambit of "processor size" independent
> variables for doing "low level" stuff - like pointer math.
qword is 64-bit
ptr
Daniel Mantione Wrote:
>This isn't true:
>* Cardinal: is always an unsigned 32-bit integer
>* Pointer: can be 32-bit or 64-bit depending on processor
>* Integer: is a signed 16-bit or 32-bit integer depending on compiler mode
And you are absolutely correct. I forget this because I have the FPC
co
Hi,
Am Donnerstag, den 22.02.2007, 13:18 -0500 schrieb Jason P Sage:
> I Hope the following never goes away - I use this stuff all the time!
>
> Types
> -
> Cardinal, Pointer, Integer
> Always evaluate to the endian in use.
> SizeOf(Cardinal)=SizeOf(Pointer)=SizeOf(Integer)
>
>
> Offsets
Op Thu, 22 Feb 2007, schreef Jason P Sage:
> I Hope the following never goes away - I use this stuff all the time!
>
> Types
> -
> Cardinal, Pointer, Integer
> Always evaluate to the endian in use.
> SizeOf(Cardinal)=SizeOf(Pointer)=SizeOf(Integer)
This isn't true:
* Cardinal: is always a
I Hope the following never goes away - I use this stuff all the time!
Types
-
Cardinal, Pointer, Integer
Always evaluate to the endian in use.
SizeOf(Cardinal)=SizeOf(Pointer)=SizeOf(Integer)
Offsets
---
If I have a record or a class - and dereference the pointer "nil" I can
always get
