Change 14626
raise exceptions in P4#run_resolve
Any exceptions raised during the block passed to P4#run_resolve were silently
swallowed. We still use 'rb_protect()' to run the block in the user's script;
however, we now stash where the exception happened in 'rubyExcept' (a member of
'ClientUserRuby') instead of just a local variable. After running a command, I
now run 'ClientUserRuby::RaiseRubyException()' - if an exception has been
caught by 'rb_protect()' we now run 'rb_jump_tag()' to jump to the exception
and raise it up.
User visible change to be documented in release notes.
Any exceptions raised during the block passed to P4#run_resolve were silently
swallowed. We still use 'rb_protect()' to run the block in the user's script;
however, we now stash where the exception happened in 'rubyExcept' (a member of
'ClientUserRuby') instead of just a local variable. After running a command, I
now run 'ClientUserRuby::RaiseRubyException()' - if an exception has been
caught by 'rb_protect()' we now run 'rb_jump_tag()' to jump to the exception
and raise it up.
User visible change to be documented in release notes.