Timeline for Exit Code Golfing
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2017 at 14:18 | comment | added | findusl | A crash is a program stopping to function properly. Your program does all that you told it to do properly, it reads one character from the input and then stops. So even though the exit code indicates an error it didn't crash. | |
| Jan 21, 2017 at 18:31 | history | edited | Dennis | CC BY-SA 3.0 |
deleted 292 characters in body
|
| Jan 19, 2017 at 21:17 | comment | added | Dennis |
@dim I guess that depends on your definition of crash. Not ending main with return or exit is an error as far as the C90 standard goes, and it results in an exit code that indicates failure. That's all a crash does at heart.
|
|
| Jan 19, 2017 at 20:43 | comment | added | Quentin | Either way, this is awesome. | |
| Jan 19, 2017 at 20:02 | comment | added | dim | That's clever. But the program doesn't actually crash, then. It returns normally, whether the spec is to "cause a fatal exception/irreversible failure/crash" | |
| Jan 19, 2017 at 17:55 | history | edited | Dennis | CC BY-SA 3.0 |
added 8 characters in body
|
| Jan 19, 2017 at 15:10 | comment | added | zeppelin |
It would be interesting to see if this can be modified to break through the 8 bit barrier, using the shell like jsh, which supports set -o fullexitcode.
|
|
| Jan 19, 2017 at 3:45 | history | answered | Dennis | CC BY-SA 3.0 |