The current error reporting is somewhat lacking...
we need to capture ALL errors gracefully and attempt to give an accurate description of what happened.
there are TWO types of errors that could occur in o-behave
compile time errors
compile-time errors should be caught by Ted and outputted in the console
run-time errors should be caught by the browser and logged to the console / written to the DOM (when appropriate). there is a bit of eval() magic happening here, so we'll need to address that first in order to better track error messages.