Name: Anonymous 2014-12-09 5:59
Where do programming language design decisions go when they die? If they're evil enough, they end up in this thread, for us to bring back to life like a bunch of bored asshole wizards with way too much free time. And if we collect enough souls from the damned, we can frankenstein them together into a programming language antichrist and chortle soundlessly as it ravages the cosmos.
Right at this moment, the feature that has captured my attention is the nonlocal goto. We all know about
Right at this moment, the feature that has captured my attention is the nonlocal goto. We all know about
call/cc, but what about putting this in a language that statically allocates its procedure activation records? I shudder to imagine the potential for control flow obfuscation in functions that "smash" their own "stacks" by recursing into (and out of) themselves. I'm so disgusted with myself I might just sit down and write an interpreter for this nonsense.