Bug 317 – Need full translation of the Windows API headers

Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P3
Component
phobos
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2006-09-02T13:36:00Z
Last change time
2015-11-03T19:30:13Z
Keywords
pull
Assigned to
smjg
Creator
smjg

Comments

Comment #0 by smjg — 2006-09-02T13:36:03Z
At the moment, std.c.windows.windows is just a disorganised, very incomplete collection of Windows API structures and functions. A project is underway to make a full D translation of the Windows API headers. While there have been a number of efforts, I feel that the one I started (see link above) is now the most developed and best designed. Once it's done, then we should make this translation part of Phobos, thereby replacing the current std.c.windows code. I feel that giving the D programming community access to the full Windows API is an important part of preparing for D 1.0. I am therefore filing this issue in order to nominate it as a 1.0 blocker.
Comment #1 by clugdbug — 2006-09-04T02:10:16Z
Personally I see that as a library blocker, rather than a language blocker, with one important exception: We need complete, up-to-date Windows import libraries, since only Walter has a license to redistribute them. Fortunately, it's also not a big effort -- just download the latest ones and convert to omf. Absence of import libs is definitely a blocker for 1.0 libraries. The community can do the headers.
Comment #2 by andrej.mitrovich — 2012-12-23T11:06:42Z
*** Issue 1988 has been marked as a duplicate of this issue. ***
Comment #3 by andrej.mitrovich — 2012-12-24T15:49:40Z
*** Issue 9202 has been marked as a duplicate of this issue. ***
Comment #4 by diggsey — 2013-05-02T17:30:15Z
Is anybody still working on this? I'd be happy to help out if there's anything I can do. It's something that I think is really quite important, especially if D is to be taken seriously.
Comment #5 by smjg — 2013-05-03T09:53:13Z
Of course, read the instructions at http://www.dsource.org/projects/bindings/wiki/WindowsApi and then assign yourself a module and have a go at translating it!
Comment #6 by diggsey — 2013-05-03T15:28:13Z
Ah good, will do. What's currently stopping this bug from being fixed? I know your project isn't finished yet but it's already far surpassed the windows bindings in druntime. With a few minor changes I managed to get it to function as a drop-in replacement. https://github.com/Diggsey/druntime-win32 https://github.com/Diggsey/druntime https://github.com/Diggsey/phobos/tree/win32-bindings Am I correct in thinking it's only available as an SVN repository on dsource? I had to clone it into a git repo so I could add it as a submodule in druntime.
Comment #7 by smjg — 2013-06-30T12:02:25Z
(In reply to comment #6) > Ah good, will do. > > What's currently stopping this bug from being fixed? Just a shortage of people who have both the time and the motivation. Which admittedly I don't understand, since I'd think there be a large base of people wanting to write powerful Windows GUI apps, and therefore wanting a complete set of Windows API bindings.
Comment #8 by andrej.mitrovich — 2013-09-25T17:10:53Z
*** Issue 11116 has been marked as a duplicate of this issue. ***
Comment #9 by destructionator — 2015-01-02T22:58:49Z
Comment #10 by dlang-bugzilla — 2015-11-03T19:30:13Z