OOLua is a test driven, cross platform, non intrusive code generator framework for binding C++ and Lua code. Code is generated via macros which internally use templates to provide type safety where possible.
The library uses the MiT licence and requires no external dependencies (of course requires Lua 5.1 or greater), or RTTI.

OOLua version 1.2.0 is released.
Speed comparisons with Swig and Luabind.
There is a known limitation of the framework.

Looks really promising, I'll have to try it out some time.

_________________
www.littlemonkey.co.nz

OOLua version 1.2.2 is a bug fix, has optimisations over 1.2.1 and now
uses premake 4.2. The use of the latest premake means that xcode is
now supported.

See profile.log for current speed comparisons with swig 1.3.40 and Luabind 0.9
Download :google code
Please see readme.txt in the download for build instructions or consult the wiki Building

Change list
*Converted premake scripts to premake4
*optimised checking of a type against a requested type via casting and storing a function taking the parameters to lua_Cfunction which requires less usage of the Lua stack.
*moved Luna licence to a more suitable section of code
*removed dead code from oolua_storage.h
*removed dead code from class_from_stack.h
*added setting a user data's none const name whilst changing it's constant status in set_type_top_to_none_const to prevent potentail errors. As the name and none constant name use a pointer compare when checking for constant status.
*added xcode support, tests required linking gtest and gmock normally i.e. -lgmock instead of gmock specified way gmock config - *
*added xcode test unit bash build script.
*build logs directed to there own directory
*added new test project "tests_may_fail" for issue 7 (http://code.google.com/p/oolua/issues/detail?id=7)
this fails soft on an error i.e. returns 0 from main not 1. moved effected tests (pushing and pulling signed int and signed long)to the new test project.
*changed bash build scripts to run the tests_may_fail swell as unit.tests
*added comment in lua_includes.h for mingw users
*added a readme with details of library as many download locations are now available
* fixed passing a c style string to a member function bug as reported by airbash http://code.google.com/p/oolua/issues/detail?id=8
* fixed a corresponding bug of a member function which returns a c style string.
* added define in lua_includes.h to support Lua 5.2 and 5.1.4 simultaneously
* fixed typo in xcode_premake4.sh
* adjusted premake recursive file inclusion to offset premake4.2 problem
* renamed gnu build script to gnu_tests.sh to reflect what it is doing
* added gnu_build.sh for building a local install
* added xcode_build.sh for building a local install
* added codeblocks_build.sh for building a local install
* renamed codeblocks_premake4.sh to codeblocks_tests.sh to reflect what it is doing
* added dl to link flags for unit tests in linux builds
* added vs2008x86_build.bat for building a local install
* renamed vs2008x86_premake4.bat to vs2008x86_tests.bat to reflect what it is doing
* added codeblocks_build.bat for building a local install
* renamed codeblocks_premake4.bat to codeblocks_tests.bat to reflect what it is doing

Thanks
Liam

edit: corrected Luabind version number

I apologise for including a link to the profile results as some people think it is just not fair and you will find the numbers confusing. I would like to add that OOLua may not be what you are looking for, but also Luabind may not!

The Luabind author is complaining because OOLua and Swig draw a line between checking what you pass to a function which requires data created by the libraries and a user passing completely incorrect data.

In a future version I will add the ability for a user to define if a check should be made on every instance passed to it that it actually created the data, this will of course impose a penalty for using the library correctly. On the other hand if it is intended to allow third parties to write scripts this could be seen as the correct action to take.

Added to branch is the ability to use constructors in Lua which was previously not a feature. For Details of constructors and other details please see [url=bit.ly/7DHWfX]this mailing list post[/url].

Feedback of any type is requested.
Thanks