Timeline for "DDoouubbllee ssppeeaakk!!"
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2021 at 1:10 | history | bounty awarded | Bubbler | ||
| S Feb 1, 2021 at 18:26 | history | suggested | Community Bot | CC BY-SA 4.0 |
replaced image with Markdown table (image is still linked) for accessibility
|
| Feb 1, 2021 at 17:44 | review | Suggested edits | |||
| S Feb 1, 2021 at 18:26 | |||||
| Aug 22, 2019 at 16:15 | comment | added | Kamila Szewczyk | Partially yes, partially no. There needs to be zero halting instruction, as this program doesn't halt. These "instructions" are serving different purpose. You might want to check this wiki page to clarify state of art a bit. Or try to analyze the code yourself (the recommended way - you will learn a lot, and the process will be really enjoyable) | |
| Aug 22, 2019 at 16:03 | comment | added | MilkyWay90 | Are those the backup I/O and halting instructions in case one of them gets modified? | |
| Aug 22, 2019 at 15:29 | comment | added | Kamila Szewczyk | @MilkyWay90 there are multiple halt, input and output instructions, because malbolge is storing data in the same memory where it stores code. Does it hint anything to you :)? | |
| Aug 22, 2019 at 14:50 | comment | added | MilkyWay90 |
How did you decrypt the code after jumping back with the i instruction (I can see a lot of p, *, and j, but how does it play into the program)? Also, why are there multiple halt, input, and output instructions?
|
|
| Aug 13, 2019 at 17:31 | history | bounty awarded | Shaggy | ||
| Aug 1, 2019 at 20:09 | comment | added | Dylan | The fact that this was done in a few hours... let alone, done at all. Phew. I read your paper on the turing completeness of seed, might you have written a Malbolge transpiler? | |
| Aug 1, 2019 at 15:35 | history | edited | Arnauld | CC BY-SA 4.0 |
fixed typos
|
| Aug 1, 2019 at 11:56 | history | edited | Kamila Szewczyk | CC BY-SA 4.0 |
Poor man's explaination; added 133 characters in body
|
| Aug 1, 2019 at 11:36 | comment | added | Charlie | Here's what the shorter code looks like when decrypted and before running it. Malbolge commands are j, i, *, p, <, /, v, o. | |
| Aug 1, 2019 at 11:35 | history | edited | Kamila Szewczyk | CC BY-SA 4.0 |
edited body
|
| Aug 1, 2019 at 9:57 | comment | added | Arnauld | +1 for "it becomes pretty trivial" | |
| Aug 1, 2019 at 9:53 | history | edited | Kamila Szewczyk | CC BY-SA 4.0 |
added 17 characters in body
|
| Aug 1, 2019 at 9:39 | history | edited | Kamila Szewczyk | CC BY-SA 4.0 |
added 4828 characters in body
|
| Aug 1, 2019 at 5:01 | comment | added | MilkyWay90 | Seriously, I've always been interested in programming in Malbolge, but I'm always confused by the docs | |
| Jul 31, 2019 at 20:58 | comment | added | Kevin Cruijssen | First time hearing of Malbolge, but reading those docs all I can think of is: dang, this is an impressive answer. Is it possible to explain your code, or is it beyond explaining? ;) | |
| Jul 31, 2019 at 20:56 | comment | added | Shaggy | @Adám, by a factor of 2, at least. | |
| Jul 31, 2019 at 20:16 | comment | added | Adám | The day that someone writes, in Malbolge, a program that simply copies its input to it's output, is the day my hair spontaneously turns green. It's the day that elephants are purple and camels fly, and a cow can fit through a needle's eye. This seems to surpass that. | |
| Jul 31, 2019 at 18:45 | comment | added | MilkyWay90 | Woah! How did you make this? How do you program in Malbolge? (these are serious questions, by the way) | |
| Jul 31, 2019 at 17:52 | history | answered | Kamila Szewczyk | CC BY-SA 4.0 |