Timeline for Challenge: Write a piece of code that quits itself
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2013 at 4:01 | comment | added | Kevin | @user1981338: the question originally had the code-trolling tag, but it has since been edited out. Now that the tag's gone, +1. | |
| Dec 30, 2013 at 0:37 | comment | added | osvein | @SargeBorsch True, but the host hasn't set any rules for what permissions the executor has. | |
| Dec 30, 2013 at 0:24 | comment | added | osvein | @Kevin code-challenge and code-trolling are different tags with different rules. | |
| Dec 29, 2013 at 17:33 | comment | added | Display Name | System processes can't be killed without admin rights, aren't they? | |
| Dec 29, 2013 at 16:08 | comment | added | Kevin | -1 (if I had the rep): The meta on code trolling says that destructive answers aren't allowed because of the risk of people trying them on their own machines. See the second bullet in the list of restrictions: codegolf.stackexchange.com/tags/code-trolling/info | |
| Dec 29, 2013 at 9:51 | history | edited | osvein | CC BY-SA 3.0 | fixed code |
| Dec 29, 2013 at 6:14 | comment | added | Breakthrough | +1 for very unconventional method of killing every single other thing, thus causing your own program to go down with the system (or at least, I assume that's the idea?). I don't have a C# runtime on this machine, but I've got to ask... In practice, does this end up taking the system down or just all running processes? (I thought C# programs invoked the interpreter themselves, thus not relying on the existence of a particular JIT/CIL process...). Again, great job thinking 'outside the box' (har har) on this one :) | |
| Dec 29, 2013 at 0:52 | review | First posts | |||
| Dec 29, 2013 at 1:36 | |||||
| Dec 29, 2013 at 0:37 | history | answered | osvein | CC BY-SA 3.0 |