Comments on Lab3

1. In Example 3 you also removed the try/catch block -1

2. Watch out for lines that are so long that they will wrap around when you print.

3. Weird font that appears when you copy from jGrasp output is not a problem.

4. Your answer in 1.7 as to why the "error" was generated at run-time (rather than at compile-time) is not really a good one. -1

5. You are missing the output Done in example3. -1

6. You have some misspellings. You will lose a point for each 3 found in your submissions.

7. Your answer isn't quite right. -1

8. You don’t have a description of what the code does. -1

9. In Example 1 you were to change the denominator to 0 and experience and then throw and catch the exception. You didn't read the directions carefully enough and fixed the "wrong" problem.

10. That solution will eliminate the error message but it doesn't help you understand WHY the message is really occurring.

11. Your output is missing the word "Done".

12. Your answer doesn't explain why you think it's working correctly. -1

13. Please make sure you have @version/date next time

14. Your answer is not complete; you didn't finish the sentence. -1

15. In 2.7, the compiler has no way of knowing whether the FOR loop will be entered. -1

16. When you are asked “did It work or not” you should explain your answer. -1

17. You forgot to put your name and Lab3 under comments when you submitted -1

18. It is because when an exception is caught by the catch block, after the code in the catch block has been executed, the program leaves the block in which the catch is nested. . As an example consider the following for ( ) try { } catch { } which is the outline of a for loop with a single try/catch in it. The block that is left is the curly braces following the catch.

19. printStackTrace is a method called by the instance of the exception object.

20. Missing why part of question. -1.

21. You didn't NEED the try catch block.

22. You left your name off your worksheet. -1