You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems like a reasonable step to me. I would suggest that it derive from std::runtime_error.
As a side note, I went looking to see how it would differ from LuaException and discovered this:
inlinevoidenableExceptions(lua_State* L) noexcept
{
#if LUABRIDGE_HAS_EXCEPTIONS
LuaException::enableExceptions(L);
#elseunused(L);
LUABRIDGE_ASSERT(false); // Never call this function when exceptions are not enabled.
#endif
}
Would it not be safer to do it this way? (Thinking about the principal of failing early, this would fail at compile time rather than run time.):
To be able to catch individual exceptions when raised by luabridge, we should create specific derived exception types.
The text was updated successfully, but these errors were encountered: