Timeline for Simple “secret message” decoder program
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2015 at 18:33 | history | edited | TheCoffeeCup | CC BY-SA 3.0 | deleted 8 characters in body |
| Jan 29, 2015 at 18:32 | comment | added | Vogel612 | don's use System.exit() in called code. Instead you should probably early return an error value and let calling code handle it. This seems to be the generally better option here, too. | |
| Jan 29, 2015 at 18:01 | comment | added | TheCoffeeCup | @200_success How about System.exit(1)? | |
| Jan 29, 2015 at 18:00 | history | edited | TheCoffeeCup | CC BY-SA 3.0 | added 8 characters in body |
| Jan 29, 2015 at 17:57 | comment | added | 200_success | But putting the catch at the end makes it obvious that an exception will make the flow jump to the end. | |
| Jan 29, 2015 at 17:17 | comment | added | TheCoffeeCup | @200_success That's why return was over there. | |
| Jan 29, 2015 at 8:41 | comment | added | 200_success | If an IOException occurs anywhere (for example, during in.readLine()), you do want the flow of control to skip over the entire body of the program. Therefore, enclosing all of the contents of the main() function in the try block was the right thing to do. | |
| Jan 29, 2015 at 3:37 | history | edited | TheCoffeeCup | CC BY-SA 3.0 | added 301 characters in body |
| Jan 29, 2015 at 3:23 | vote | accept | quidproquo | ||
| Jan 30, 2015 at 2:43 | |||||
| Jan 29, 2015 at 3:21 | history | answered | TheCoffeeCup | CC BY-SA 3.0 |