Re: Lua binding compare-and-contrast

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

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

On 12/15/2010 4:19 AM, liam mail wrote:

> My observation for Open Source projects is that a large number do not
> get a lot of feed back until something does not work, so I would be
> really interested in what you found awkward to use with OOLua so that I
> may address any issues.





Well, the fact that you need to list every function twice, figuring out
which list to put it in the second time, is awkward. The fact that you
need to list parameters for functions is awkward.

SWIG and tolua++ allow you to copy-and-paste from headers, which means
even though they require the same information, it's far less awkward to
supply it. And LuaBind does reflection to detect the parameters. I want
to be able to list the functions I'm using, AT MOST, once. In OOLua you
not only have to list them twice, but once they go in a header, and once
in a compiled file; as far as I'm concerned the header/implementation
separation of C/C++ is a design flaw, and that basically ends up
doubling the impact of it, since each new function you write now needs
to be in four places instead of one.

And the complete lack of up-to-date documentation is a real bummer.
"Read the tests" does not substitute for clear (indexed!) documentation
IMO. Sorry.

> PS the OOLua link in the blog post is broken,




Thanks; fixed.

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

iQEcBAEBAgAGBQJNCOUzAAoJENSbqLBCyKKs1qQH/Arol9SMEhH22KPvZpUV/JuH
ubQvzM7UK++GjZNIxVAPf8jbb6CU0Erxv252qeKCykfTVpba3PnXQ2i711/huUvA
bQ0XZF6Bqj8ZsNL7mHHH4MKDQh6WdvtzSeTAoxLS7IT/JASQ1uNugRc9tDiCnaq6
IEWJwstG6OwmH8C+Fg9kjUG+fvtJ5hopglGl8aTsNW+nBm0Mi2RV8qG147omDPHE
Q5rUzzZyyFHqJw5NliQdIZzCpc/bRI/sxeAJ9H9zM+6Th+n51eriTqRT4MNwHT3i
sjWYTsXt8VBAF5pDtCQGOvbiIo128OfON2ShcLBrODEWNgm55yB3vuHDnwP4xpQ=
=6vW2
-----END PGP SIGNATURE-----