PureBasic Forums - English

Should they behave the same way?

Compiled as a 64 bit executable they both should behave the same.

that is, an integer in a 64-bit os will be like a quard and in a 32-bit os it will be like a long?
if so, why was it invented?

Yes, that's correct. I was invented so it can be easily used to store handles and pointers which always have the same size as the underlying architecture.

So if you write `handle = CreateWindow(#PB_Any, ...)` then `handle` should be an integer.

ok, but then is quard the same number in 32-bit and 64-bit?
I would check it myself, but so far there is nothing.

mestnyi wrote: Mon Nov 04, 2024 5:49 pm ok, but then is quard the same number in 32-bit and 64-bit?
I would check it myself, but so far there is nothing.

No, a quad is always 8 bytes. Directly from the documentation:

Long
.l
4 bytes
-2147483648 to +2147483647
Integer
.i
4 bytes (using 32-bit compiler)
-2147483648 to +2147483647
Integer
.i
8 bytes (using 64-bit compiler)
-9223372036854775808 to +9223372036854775807
Quad
.q
8 bytes
-9223372036854775808 to +9223372036854775807

Have you ever looked in the Help about variables

https://www.purebasic.com/documentation ... ables.html

infratec wrote: Mon Nov 04, 2024 8:10 pm Have you ever looked in the Help about variables

https://www.purebasic.com/documentation ... ables.html

I looked in, of course.

An 'integer' variable is used to have a standard syntax :
- boolean use
- bitwise masking from 0 to 31

--> whatever the OS, it is same source syntax.

Now, however, we cannot do lots of other use.

1) A sign treated on X86, but not on X64 : 2) A high DWORD treated on X64, but not on X86 To conclude : whatever 32 or 64 bits, use integers for numeric value between -2giga and +2giga. And use integers for 32-bits masks.

If you want to manage bigger values, force the 'quad' type.