Stewart Gordon wrote:
On 08/02/2011 22:31, Matthias Pleh wrote:
<snip>
VisualD has some code for automated winapi-conversion:
<quote>to build the necessary D translations from the Windows and
Visual Studio SDK</quote>
<snip>
Firstly, can this be used to build D translations from headers other
than M$'s own? The win32 translations in the bindings project is based
on the MinGW headers, therefore avoiding copyright issues.
I guess it can be tweaked without too much effort to work with the MinGW
headers. It seems, the mingw-files are missing a lot from the SDK,
though. The win32api-3.15 folder has less than 3 MB in <250 files, while
the SDK v6.0A which comes with VS2008 has >60MB, just counting the 1200
header files. The current v7.1 has a lot more, but I don't have it on
this computer to check.
Secondly, automated translation leaves a lot to be desired, and the
whole point of the project is to avoid these shortcomings.
The mingw win32api files are very terse, so there is not a lot to be
lost. But the conversion tool tries to keep comments and formatting as
much as possible.
Agreed, you can't be sure translation was correct in all cases, but
there is so much of it, you don't want to do it manually...
