On 12/05/2012 19:47, Gor Gyolchanyan wrote:
I'll just move the binding to druntime and rename the package from win32.* to core.c.windows.* There are tons of modules, each for a header file in original WinAPI.
<snip>
You mean you're going to try merging the bindings into your installation of druntime and see if it works, in order to see whether there are complications that need to be overcome?
On Sat, May 12, 2012 at 10:43 PM, Jonathan M Davis <jmdavisp...@gmx.com <mailto:jmdavisp...@gmx.com>> wrote: <snip>
What kind of requirements are you worried about? We want all of the Win32 API bindings in druntime in an organized manner (my first guess would be according to the dll or header that they come from in C, but I don't know how the bindings project does it or necessarily what the best way is).
This is indeed how the WinAPI bindings project is organised - each file is a translation of the C header of the corresponding name. And yes, it was started with a view of putting it into Phobos when it's ready (druntime didn't exist back then).
I don't believe that what's currently in druntime is necessarily organized properly (I don't think that where new declarations go has been all that organized), so some stuff will likely have to be moved around when the WinAPI bindings are merged in (with the appropriate deprecation path used for any declarations that must be moved). But really, it's just a question of someone taking the time and making the effort to merge the WinAPI bindings into druntime and creating a pull request for it.
What's going to happen about continued maintenance of the bindings once they've been dropped in? Are we just going to carry on maintaining the bindings on dsource and then make pull requests every now and again to update druntime to it?
There are a few things that still need to be thought about, like how handle types are defined. Better to get this decided before we drop it into druntime. I'll start another thread about this and other issues.
Stewart.
