lean2/src/bindings/lua/util.h

/*
Copyright (c) 2013 Microsoft Corporation. All rights reserved.
Released under Apache 2.0 license as described in the file LICENSE.

Author: Leonardo de Moura
*/
#ifdef LEAN_USE_LUA
#include <lua.hpp>
namespace lean {
void setfuncs(lua_State * L, luaL_Reg const * l, int nup);
/**
   \brief Wrapper for invoking function f, and catching Lean exceptions.
*/
int safe_function_wrapper(lua_State * L, lua_CFunction f);
template<lua_CFunction F> int safe_function(lua_State * L) {
    return safe_function_wrapper(L, F);
}
}
#endif
feat(lua/util): remove dependency on luaL_setfuncs Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-03 20:16:23 +00:00			`/*`
			`Copyright (c) 2013 Microsoft Corporation. All rights reserved.`
			`Released under Apache 2.0 license as described in the file LICENSE.`

			`Author: Leonardo de Moura`
			`*/`
			`#ifdef LEAN_USE_LUA`
			`#include <lua.hpp>`
			`namespace lean {`
			`void setfuncs(lua_State * L, luaL_Reg const * l, int nup);`
feat(lua): add safe_function template that catches Lean and C++ exceptions and convert them into Lua errors I'm using the approach described at: http://stackoverflow.com/questions/4615890/how-to-handle-c-exceptions-when-calling-functions-from-lua BTW, in some Lua versions, the C++ exceptions are correctly propagated. I think we should not rely on features of particular implementations. For example, LuaJIT does not propagate C++ exceptions. Whenever an exception is thrown from C++ code invoked from LuaJit, LuaJit interrupts the execution and converts it to an error "C++ exception". On the other hand, Lua 5.2 PUC-Rio interpreter (for Ubuntu) seem to propagate the C++ exceptions. The template safe_function solves the issue. It will also produce a Lua error whenever the function being wrapped throws an exception. The error message is based on the "what()" method. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-03 22:42:54 +00:00			`/**`
			`\brief Wrapper for invoking function f, and catching Lean exceptions.`
			`*/`
			`int safe_function_wrapper(lua_State * L, lua_CFunction f);`
fix(lua): problem when compiling with clang++ Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-04 23:05:04 +00:00			`template<lua_CFunction F> int safe_function(lua_State * L) {`
feat(lua): add safe_function template that catches Lean and C++ exceptions and convert them into Lua errors I'm using the approach described at: http://stackoverflow.com/questions/4615890/how-to-handle-c-exceptions-when-calling-functions-from-lua BTW, in some Lua versions, the C++ exceptions are correctly propagated. I think we should not rely on features of particular implementations. For example, LuaJIT does not propagate C++ exceptions. Whenever an exception is thrown from C++ code invoked from LuaJit, LuaJit interrupts the execution and converts it to an error "C++ exception". On the other hand, Lua 5.2 PUC-Rio interpreter (for Ubuntu) seem to propagate the C++ exceptions. The template safe_function solves the issue. It will also produce a Lua error whenever the function being wrapped throws an exception. The error message is based on the "what()" method. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-03 22:42:54 +00:00			`return safe_function_wrapper(L, F);`
			`}`
feat(lua/util): remove dependency on luaL_setfuncs Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-03 20:16:23 +00:00			`}`
			`#endif`