Next updatet

[Danilo]

C's Int type is the same as PB's Integer.

C's data types can be different size on different platforms, so 'int' can be 16bit on one platform and 32bit on another platform.
On Windows 'int' is 32bit with VisualC++ 32bit and 64bit, so it is not like PureBasic's .i Integer.

For Windows, see also MSDN:

• Data Type Ranges
• Fundamental Types (C++)
• Windows Data Types

[Thorium]

The problem about integrating a 128 Integer type can't be done with a single ASM instruction. In fact this is why we don't have an "Unsigned Long" and an "Unsigned Quad" type in PB.

Actualy you can integrate unsigned longs with a single instruction. They are not implemented because Fred dont knows a good/easy/fast way to do mixed caluclations with signed and unsigned variables and because PureBasic is a BASIC after all, he dont wants to restrict the programer in only using signed or unsigned in a single equation. That is basicly what he has written why he didnt included them.

For the C "long double" seems to be outdated these days, so why just to create 128 floating point type instead even if SIMD commands are needed ?

SIMD dosnt support 128bit floating point types. It does support packed 128bit variables, which means that in one 128bit variable you have two 64bit or four 32bit floating point numbers. As i said 128bit registers are not meant for basic 128bit types.

As Ramihyn_ pointed out you can implement any size of type. There are large number libs available.

I just wanted to tell that just because there are 128bit and 256bit registers it doesnt mean large number types will be implemented. At least it doesnt make it easier to implement them.