You donât know how he does stuff like this. What does this even mean? Itâs nonsense. Is it even syntactically viable?? Are you allowed to color text like that??? ARGH. Maybe you should ask him about it some time.
You see, at first glance, this code does look syntactically viable, but only if we donât pair the brackets in the way the coloring implies. If we write the code like this:
Then itâs a loop bound to the lifespan of Universe 1. Inside that main loop, itâs running a loop bound to the inverse of Universe 2âČs lifespan - my guess being that this loop only runs while Universe 2 is dead.
If Universe 2 is ever registered as âaliveâ, the program waits for the blue THIS to die, and then continues. And when the main Universe 1 loop ends, it will wait for the red THIS to die, and finally exits.Â
In other words: This program will exit when U1 is dead, U2 is alive, and both âbifurcatedâ iterations of THIS are dead.Â
However, the red/blue coloring implies that the brackets are paired in a completely nonsensical way.Â
Iâm with Karkat here, This is nonsense. You canât put the top half of one code block inside another - at least, not in any language Iâve worked with. Iâm sure there are weird, esoteric languages that do it, but itâs definitely not the syntax du jour.
This âmerged bracketâ interpretation is probably the correct one, though, since the colors match up. The reason this compiles at all is probably due to the special behavior of bifurcate THIS[], which weâre not privy to.Â
I do have a theory about what bifurcate is doing here, but⊠oh my god , guys, this is so silly. Will I post it? Iâm going to post it.Â
TA wears 3D glasses, right?
What if weâre meant to do the same?
If we view these two loops as not inside each other, but adjacent to each other in 3D space, then this code makes a lot more sense. Suddenly weâre just looking at two simple death loops - one which which exits when U1 dies, and one which exits when U2 lives.Â
Theyâre not blocking each other, because theyâre probably executing on different threads, which may be the true function of bifurcate. Viewed like this, this code becomes a simple, multithreaded script that works similarly to my original interpretation - the difference being that now, the colors match up properly. Itâs kind of beautiful, to be honest.Â
Now that Iâm viewing this program as two threads, it seems as if the blue loop waits for the red thread to die before it can exit, and vice versa.Â
If Iâm right about this, it means that this program is deadlocked - neither thread can exit, because itâs waiting for the other one. The two threads are back to blocking each other, and this program will never exit. Â
This code, when executed, immediately causes the userâs computer to explode, and places a curse on the user forever, along with everyone he knows, and everyone heâll ever meet.
Not surprisingly, later on you would run this code in a fit of stupidity.
None of this, however, explains why it curses the user.Â
I think I need to borrow Karkatâs ~ATH manual.Â