[maksim]

Hello!

They say that for long type in *.h file we should use int in *.d file:
http://www.digitalmars.com/d/2.0/htod.html

But in some files in this project long and ulong types are used for long and unsigned long C types.

So, what way is correct?

[maksim]

Well, on my 64-bit platform:
C:
sizeof(int) = 4
sizeof(long) = 8
D:
int.sizeof = 4
long.sizeof = 8

So there is no problem if I compile my code with 64-bit libraries.

As far as I know, on 32-bit platforms sizeof(long) = 4 in C, but in D it's still 8 bytes.
May be it's better to have the following code somewhere?

[doob]

In D the size of types is always fixed, so in D the size of int will always be 4 and the size of long will always be 8. This is not the case in C. In C it depends on the platform is 32bit or 64it and if it's 64bit it depends on the data model that is used. There are four data models that exist but it's basically only two you need to worry about. They are:

LLP64 - used on Windows
LP64 - used on Posix

So you can use the following code to correctly bind C functions using the "long" type:

[maksim]

Thank you!

Edited:
It doesn't work. Features like "(void*).sizeof" and "version( X86_64 )" depend on complier not CPU or OS.
I use a 32-bit D compiler and it says "(void*).sizeof = 4", though my CPU and OS are both 64-bit.
When you link a program with C libraries you should find out the version of each library and indicate them explicitly:

In the program:

[doob]

Well, yes, "(void*).sizeof" would depend on the compiler and not on the CPU or OS. But, you should only link 32bit libraries with other 32bit libraries, even if you're running a 64bit OS. Currently DMD is only 32bit which mean you should link to other 32bit libraries regardless if you're OS is 64bit or not.