Timeline for Make your language unusable
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2021 at 14:47 | comment | added | Oskar Skog | Can the program die by SIGSEGV and SIGILL? This would allow the program to give a single binary output. | |
| Oct 2, 2016 at 13:14 | comment | added | zwol |
@JesseTG Are you familiar with strace?
|
|
| Oct 1, 2016 at 3:12 | comment | added | JesseTG | You know, I think this could actually be used to debug syscalls or programs that directly use them. | |
| May 28, 2016 at 14:21 | comment | added | The Fifth Marshal |
Note that this program only meets the spec if -e is specified and no other options. If -a or -d is specified, the log of allowed or denied syscalls can be used as an output form. If -e isn't specified, a binary exitcode-like output is allowed by either killing itself with kill() or using exit(), which would produce two different exit codes.
|
|
| Mar 3, 2016 at 10:44 | history | edited | Toby Speight | CC BY-SA 3.0 |
Add prettify hint
|
| Jan 24, 2016 at 20:15 | history | edited | zwol | CC BY-SA 3.0 |
deleted 9 characters in body
|
| Jan 24, 2016 at 4:02 | comment | added | zwol | @Joshua That's clever, and would be difficult to prevent using this approach (since the program is just modifying its own memory) but it's not currently on the list of "allowed output methods." | |
| Jan 8, 2016 at 22:04 | comment | added | Joshua | I can generate output with this. I write to my command line. The output is visible in ps! | |
| Oct 23, 2015 at 13:18 | history | edited | zwol | CC BY-SA 3.0 |
deleted 108 characters in body
|
| Oct 22, 2015 at 21:36 | comment | added | zwol | @BlacklightShining I thought about it some more and I rewrote the program basically from scratch. It's rather cleverer now what it does and (I hope) meets even the most stringent reading of the challenge. | |
| Oct 22, 2015 at 21:35 | history | edited | zwol | CC BY-SA 3.0 |
version 2.0 rather more sophisticated
|
| Oct 22, 2015 at 5:31 | comment | added | Blacklight Shining |
…oh, I missed that. With -DNO_EXIT, this does break the language. Can't change my vote without an edit, though…
|
|
| Oct 21, 2015 at 20:36 | comment | added | zwol |
@BlacklightShining I think that this accomplishes such a huge restriction relative to normal behavior that it should be acceptable even though, as you say, you could still write a prime tester, but -DNO_EXIT mode is for people who feel as you do. No meaningful output is possible in that mode.
|
|
| Oct 21, 2015 at 19:36 | comment | added | Blacklight Shining | “the target can read its command-line arguments, perform pure computations, and produce an 8-bit exit status, but will not be able to allocate memory or do I/O”—I dunno, I think you still meet the four criteria. Integers can be interpreted from commandline arguments; the exit status can be leveraged for simple output; addition isn't hindered; and all you need for a primality test is the ability to do pure computations, a bit of stack space, and a loop. | |
| Oct 21, 2015 at 17:49 | history | answered | zwol | CC BY-SA 3.0 |