Timeline for Challenge: Write a piece of code that quits itself
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 29, 2013 at 1:55 | comment | added | Johannes | The program neither throws an error nor does it cause an error within the program. The system can not handle it. | |
| Dec 28, 2013 at 23:07 | comment | added | John Dvorak | I believe the rule encompasses both, however. Can the asker clarify? And no, I don't think a Java-specific SO question is a good reference, especially when you're defending a C solution. | |
| Dec 28, 2013 at 23:06 | comment | added | syb0rg | @JanDvorak There are differences between errors and exceptions. | |
| Dec 28, 2013 at 22:58 | comment | added | John Dvorak | "Quitting by throwing exceptions won't be accepted any more!" and this includes out-of-memory errors | |
| Dec 28, 2013 at 22:28 | history | answered | Johannes | CC BY-SA 3.0 |