-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminate only when callback wasn't set #37
Comments
I must confess I don't know the implications, since I generally only use the exception path. |
Yes, we can make error handler to return boolean value, and if it's false (or callback wasn't even set), then calls to std::terminate. Implications:
|
Okay, I think I will replace cast_failed_callback and error_callback with std::function<bool( ... )> counterparts and disable terminate on true return value (ie. it has "disable terminate" semantics). |
Sure |
Currently when luabind exceptions are disabled, program terminates always on lua errors.
Maybe we can allow user to tell luabind crash only when error callback wan't set?
For now, I have modified the code for me: https://github.com/Xottab-DUTY/luabind-deboostified/commit/ee8a074be60ab849b2f4c7bba79b8c6001bf74c3
But this changes original behavior. We need a
savesafe method to change that behaviour.The text was updated successfully, but these errors were encountered: