• new (2/2) Jun 16 2013 hi,
• =?UTF-8?B?QWxpIMOHZWhyZWxp?= (4/6) Jun 16 2013 I don't think header files differ that way. Also, the are no header
• PewPew (5/7) Jun 17 2013 You can use win api directly.
• Mike Parker (14/16) Jun 17 2013 This is wrong. The *A functions deal with ascii strings, whereas
• new (1/1) Jun 17 2013 thank you all for your help.

"new" <new new.com> writes:

hi,
are there any 64bit windows header files availabe?

=?UTF-8?B?QWxpIMOHZWhyZWxp?= <acehreli yahoo.com> writes:

On 06/16/2013 09:44 AM, new wrote:
 hi,
 are there any 64bit windows header files availabe?

I don't think header files differ that way. Also, the are no header 
files in D, but "modules".

Ali

"PewPew" <PewPew example.com> writes:

On Sunday, 16 June 2013 at 16:44:59 UTC, new wrote:
 hi,
 are there any 64bit windows header files availabe?

You can use win api directly.

32/64 bit handled by defines, __WIN32__ etc.
FucnA - for 32 bit, FuncW - for 64 bit.

In D: version(...){ ... }

"Mike Parker" <aldacron gmail.com> writes:

On Monday, 17 June 2013 at 07:46:46 UTC, PewPew wrote:

 32/64 bit handled by defines, __WIN32__ etc.
 FucnA - for 32 bit, FuncW - for 64 bit.

This is wrong. The *A functions deal with ascii strings, whereas 
the *W functions deal with unicode strings. Functions that 
neither return nor accept strings do not have A/W variants.

Also, __WIN32__ does not indicate a 32-bit platform. 
Traditonally, it referred to the Win32 API, which once upon a 
time did mean a 32-bit platform, but officially that API is now 
referred to as the "Windows API", a combination of Win32 and 
Win64. __WIN32__ is always defined even on 64-bit Windows. You 
can read more about the difference here at the MS technet[1].

Essentially, any Win32 API modules created to interface D with 
that API can be used on both 32- and 64-bit. The functions are 
the same.

[1] http://technet.microsoft.com/en-us/library/bb496995.aspx

"new" <new new.com> writes:

thank you all for your help.