Re: Lua binding compare-and-contrast

[Tim Mensch <tim-lua-l@...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/15/2010 4:52 PM, liam mail wrote:
> The two awkward aspects which you identify are a mostly the result of
> the design for the library to fit it's requirements. 

Sure. I understand it works that way because it's the way you want it to
work. But you asked. :)



> The facts are that
> for Lua to call C/C++ functions by name then generally a string and a
> function address are required. Now comparing how apple and orange
> implementations do this when they use different binding strategies is
> interesting although not really relevant;  yet I agree that supplying
> the function name information in two places is not ideal but this is
> just something which OOLua has to live with. Automatic bindings that
> have a preprocess that add this data for you whilst runtime constructed
> containers of attributes and functions take the information which you
> provide. It is whoever possible to enter the data a second time in the
> header but none the less it is still required to be initialised
> somewhere and as you correctly mentioned C++ has a one definition rule.
> OOLua is not an automatic binding and also does not use a runtime
> assembled proxy class.



> I have communicated with you before and therefore we both know how each
> other feels about documentation. In my eyes it is a liability that has
> the potential to be always wrong, whilst unit tests always show the
> correct behaviour and usage otherwise there is a bug; on the other hand
> you like to have reams of documentation on everything. There is some
> documentation for OOLua yet it is not a complete reference and is in the
> form of a cheat sheet or getting started document. 

> I thank you for highlighting the issues which you had problems with. If
> you do consider these awkward aspects it maybe the result of a bad
> design in the library; yet it does fill all my requirements and I
> realise that not everyone will feel the same or have the same requirements. 

> Thanks Gaspard for mentioning dub, I will have to see if this is the
> holy grail of C++ and Lua automatic bindings everyone is looking for.

> Liam

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNCo+zAAoJENSbqLBCyKKsafwH/3tYS/rYT0e+pH/PPtnlsE4Y
J5Mu/xc+jqd2OEyhy2zv0qH6mE2PVLxMSlwvUsLm7iKD1+eS2PXWkUZfsRDdySig
b75MT23svTy3eBo0nFblmPg+bY/fHQlM0UguRkErJn7wr+mny18OQMjOuuPQ+3kD
cKD/ZuNbm6TxKw5+YSalr0IhxoMCXDmHNyHje4l7eSzOl3kDWz+lPaRiy2gPgq1R
bfX4NFxGlrcrUXWSQqw3dqYaqSfjc7pfCAlmnisFCeoiiCstCrOaEJzUAZJ0Rr/X
INcwunYAVcG7Y037W1HXZiE3CPs6IWOn/HRXhUq1idLPBVknEqx5TojuUqLvU+I=
=DE6K
-----END PGP SIGNATURE-----