6712ebe0bd
`#` == __len `[key] = value` == __newindex `key` == __index are not working properly for some reason, will need to investigate more deeply to find out why on bright side all tests pass including new tests added (for take/return std::function) fixed some things forgot to change with addition of upvalue_t for clarity (see previous commit about userdata/lightuserdata vs upvalue) |
||
---|---|---|
Catch@a6d74bd55a | ||
examples | ||
sol | ||
.gitignore | ||
.gitmodules | ||
bootstrap.py | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
ninja_syntax.py | ||
README.md | ||
sol.hpp | ||
tests.cpp |
Sol
Sol is a C++ library binding to Lua. It currently supports Lua 5.2. Sol aims to be easy to use and easy to add to a project. At this time, the library is header-only for easy integration with projects.
Sneak Peek
#include <sol.hpp>
#include <cassert>
int main() {
sol::state lua;
int x = 0;
lua.set_function("beep", [&x]{ ++x; });
lua.script("beep()");
assert(x == 1);
}
More examples are given in the examples directory.
Features
- Supports retrieval and setting of multiple types including
std::string
. - Lambda, function, and member function bindings are supported.
- Intermediate type for checking if a variable exists.
- Simple API that completely abstracts away the C stack API.
operator[]
-style manipulation of tables is provided.- Support for tables.
Supported Compilers
Sol makes use of C++11 features. GCC 4.7 and Clang 3.3 or higher should be able to compile without problems. Visual Studio 2013 with the November CTP should be able to support this as well.
Caveats
Due to how this library is used compared to the C API, the Lua Stack is completely abstracted away. Not only that, but all Lua errors are thrown as exceptions instead. This allows you to handle the errors gracefully without being forced to exit.
It should be noted that the library itself depends on lua.hpp
to be found by your compiler. It uses angle brackets, e.g.
#include <lua.hpp>
.
License
Sol is distributed with an MIT License. You can see LICENSE.txt for more info.
TODO
- Possibly document functions and classes via doxygen.
- Provide more examples to showcase uses.