4 files, each with a different language. Each file will call the next file, and then commit die. Like this:
**main.cpp** run main.py kill itself **main.py** run main.rb kill itself etc.
Basically how this works is each file calls 2 shell commands, one to run the next file, and one to commit toaster bath. The bash command to commit skydiving without a parachute is
I also added brief comments on how the shell commands work in each language so you might learn something.
I'm just bored.
There's basically two types of languages: "// for comment" languages and "# for comment" languages
map toUpper "squid" is the canonical way to do it. The goal of idiomatic Haskell code is to remove as many named variables as possible — defining
uppercase_letter letter is verbose, if you really wanted to do it that way you'd do
map (\letter -> toUpper letter) "squid", but
(\letter -> toUpper letter) is the same as just
toUpper. Yeah, coming from low-level languages Haskell probably seems weird, however it's way cleaner and if you use it enough it's the low-level languages that start to seem weird :D
@DynamicSquid smh true believers use
(\var -> (\var -> [code that uses "var"] ) 3) 5
You must feel the cleanliness of the lambda calculus course through you before you prepare to do the trivial mortal task of code production, or else you will forever live in the land of anguish and never reach functional nirvana. Do that which is functional, let the bindings of imperative programming break loose, and you shall then reach inner peace with the computers.
...Or just use a bunch of random
do blocks, whatevs honestly