sclasen/swf4go — pull request #6 by sclasen (2014-10-27 16:14:56+00:00)
Title: First cut at tight error handling.

When an error occurs, we collect the details, and then self-signal the workflow with the error details.

TODO: FSM should notice error event markers and use the ErrorHandler appropriately, perhaps transitioning to a (canned?) error *FSMState that knows how to
deal with the signal