For the genuinely confused.
Part of what makes scheme such a bloody mess is the variable situation. If you’ve ever found yourself chewing at the curtains wondering why, dear god, why the console won’t stop with the unbound variable errors, chances are something is wrong with the way you wrote one or all of your variables.
That’s why I’m doing a short walk-through of scheme variables. Local ones, anyway.
For my first script of the new year, I started learning an entirely new language for an entirely different program that has resulted in my enduring a genuinely disturbing number of migraines over the last few days.
Tangential Warning: I don’t recommend scheme for beginners. I wouldn’t recommend it for any living creature because scheme is a monumental asshat of a language. It demands that you restructure the way you write math. Who the HELL decided THAT was a good idea? Oh, everyone in the world is accustomed to writing 2+2? Fuck those bastards, we’re going to force them to do +2 2 because programming is SUPPOSED to be confusing. And just to make it extra fun, EVERYTHING needs to go in parentheses. That way, even if the morons manage to get the expressions figured out, they’ll still have to spend HOURS guessing where the missing ) needs to go.
I loathe ComputerSpeak.
Missed commas. Misspelled commands. A { instead of a ( because those bastards look exactly alike. Opening the script guarantees that I will make at least one of these errors while updating the code to do something slightly different.
So in order to combat this, I’m making my script a muzzle.
Call it a GUI (Graphical User Interface), call it a window, call it a box-it’s all the same to me. Essentially I’m turning this jumble of script on the right to this nice, soothing thing on the left.
In the interest of keeping it simple, let’s make the simplest GUI possible and build up from there.
gifGuide2Code 