Menu
▾
▴
#40 Better interactions error messages
We should study all the different kinds of error
messages you can get in interactions, and customize
them to be better.
Also, we need to resolve what to do with the stack
trace -- right now we clip it, to get rid of useless
info due to the interpreter, but I think we may clip
too much sometimes.
We also could present a better message when there is a
syntax error, hopefully by telling the student what
exactly went wrong (or at least where!).
This will likely involve either modifying DynamicJava
or yet more extension.
Logged In: YES
user_id=429731
A preparser on the interactions pane could provide a lot of
useful functionality towards this. It would not only let us
display some more useful errors in many cases, but we could
also support GJ/NextGen style generics. We'd like to see
this accomplished in 312 this spring.
Logged In: YES
user_id=430778
Yeah, so we did it. See the Interactions Pre-processor area
for more info.
Logged In: YES
user_id=429731
I'm going to re-open this. The new interactions pre-processor
framework is great, and the syntax error highlighting is
definitely an improvement. However, I don't think the actual
messages have improved at all. We're just printing out the
stream of tokens that the user typed in, not giving any
diagnostic message. I think this can (and should) be
improved.