RE: Common FFI declarations
- From: William Adams <william_a_adams@xxxxxxx>
- To: <luajit@xxxxxxxxxxxxx>
- Date: Wed, 9 May 2012 16:55:58 +0000
Hero points for you dude!! As the pharaohs used to say "so let it be written,
so let it be done..." No matter how you did it, now there it is. Funny thing
is, now that it's in this form, it would be fairly straight forward to
reconstruct a .idl file from this description :-) You've just saved me tens of
tedious hours of work, and made these fun interfaces available to the masses.
This should definitely go into the Windows ffi library. -- William
===============================
- Shaping clay is easier than digging it out of the ground.
http://williamaadams.wordpress.com
http://www.thingiverse.com/WilliamAAdams
https://github.com/Wiladams
> Date: Wed, 9 May 2012 17:48:28 +0100
> Subject: Re: Common FFI declarations
> From: corsix@xxxxxxxxxx
> To: luajit@xxxxxxxxxxxxx
>
> On Wed, May 9, 2012 at 2:19 PM, William Adams <william_a_adams@xxxxxxx> wrote:
> > I want to do Direct2D, and I wasn't looking forward to having
> > to code up all that gunk. Doing this declaratively makes it much easier.
> > Also, bonus if someone writes an IDL parser to generate the declarations in
> > your style. Then things can come in a lot quicker.
>
> As it happens, I've recently done code generation based on the
> Direct[2D|3D|Write] interfaces, which I've rehacked to spit out these
> COM descriptors rather than spitting out what it used it. The result
> is Direct2D, DirectWrite, Direct3D10.1, DXGI, WIC:
> http://pastebin.com/nipPL3TD
>
> My copy of the Windows SDK didn't include IDL files for Direct2D or
> DirectWrite, so these are all done from headers rather than IDL files.
>
Other related posts:
