Errors+and+Debugging

Students will learn the differences between syntax, run-time, and logic errors. They will also learn how to debug programs.

//**Pages:**//
 * 1) Introduction
 * 2) Syntax Errors
 * 3) Identify/Debug Syntax Error Practice
 * 4) Run-time Errors
 * 5) Identify/Debug Run-time Error Practice
 * 6) Logic Errors
 * 7) Identify/Debug Logic Error Practice
 * 8) Identify Error Final

//**Content:**//
 * 1) //Introduction --// This will have something about errors,
 * 2) //Syntax Errors --// Explanation of syntax errors.
 * 3) //Debug Practice/Identify the Error Game --//
 * 4) //Run-time Errors --// Explanation of run-time errors.
 * 5) //Debug Practice/Identify the Error Game --//
 * 6) //Logic Errors --// Explanation of logic errors.
 * 7) //Debug Practice/Identify the Error Game --//
 * 8) //Identify Error Final --// This will include all three types of errors, and will ask you to identify type, and possibly ask you to correct it.

Vicki: Being able to understand error messages is very important. What would be nice is to show an error message and let them fix the problem (and recompile). Right now we can't do that very well, unless we used Inettest.. I can see it as a collection of error messages/code that people contribute and you are asked to identify the error. The problem is there is no feedback, unless the answers are canned. Let's think on how this could be done.

Mr. Weeks: I think this would also have great potential. Does the bug hunt system address some of these or could it be modified to? I haven't seen it operate as a participant like our students have, but would certainly like to.

Maybe we could use inettest and have the code already complete with the different types of errors (well, syntax and logic anyway) and then have them identify them. Or they could maybe be canned within some random factor so they are a little different each time.