will the sorry state of the win64 headers and programs like dfl
be fixed or is it time to leave the language to linux and move on
to something else?

i agree with you, but you should have posted in "announce", so that adrei can use it for some marketing.
i too wait now for a long, long time to use it with win64. i am also giving up - i guess it will stay a linux/apple show.
maybe, as a multiple os compiler, you can use lazarus or code typhon.
cheers.


On Monday, 9 June 2014 at 15:04:19 UTC, trail wrote:
> will the sorry state of the win64 headers and programs like dfl
> be fixed or is it time to leave the language to linux and move on
> to something else?

On 6/9/2014 11:42 AM, lurker wrote:
> i agree with you, but you should have posted in "announce", so that
> adrei can use it for some marketing.
> i too wait now for a long, long time to use it with win64. i am also
> giving up - i guess it will stay a linux/apple show.
> maybe, as a multiple os compiler, you can use lazarus or code typhon.
> cheers.
>
>
> On Monday, 9 June 2014 at 15:04:19 UTC, trail wrote:
>> will the sorry state of the win64 headers and programs like dfl
>> be fixed or is it time to leave the language to linux and move on
>> to something else?
>

Clang can parse windows.h these days, it might be worthwhile to use their toolchain to dump the various SDKs of windows.h into some kind of database with it, and write an exporter for the database to D.   I imagine there is some overlap here that other languages could use something like this to provide up to date windows bindings (MingW in particular, and anyone else making new languages)

I'm sure some hand additions would need to exist but a huge amount of the API could probably be handled with something like that.