Skip to content


Subversion checkout URL

You can clone with
Download ZIP


better error reporting / error messages #1

Marak opened this Issue · 0 comments

1 participant


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
run-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.