WinAPI grossly lacking in core.c.windows.windows

[Gor Gyolchanyan]

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.
Next, we're gonna have to update the libs. What does it take to update the
libs? Are there any legal or technical difficulties?

On Sat, May 12, 2012 at 10:43 PM, Jonathan M Davis <jmdavisProg at gmx.com>wrote:

> On Saturday, May 12, 2012 22:28:12 Gor Gyolchanyan wrote:
> > There is a very good binding of WinAPI in dsource.org in bindings
> project.
> > It's aim is to precisely replicate the WinAPI's headers.
> > What are the requirements of the druntime WinAPI? What needs to be done
> to
> > get the existing binding into druntime?
>
> 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). 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.
>
> - Jonathan M Davis
>



-- 
Bye,
Gor Gyolchanyan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20120512/f2ead80d/attachment.html>