proj-oot-ootTutorial

Oot Tutorial

"New languages are always claimed to be “simple” and to become useful in a wider range of real-world applications they increase in size and complexity." -- Bjarne Stroustrup

One of the main things about Oot is it is simple; the whole language 'fits in your head'. How do we back up that claim? Here is our promise to you: this tutorial contains all of Oot. Not in the sense of a specification; this tutorial won't unambiguously define how Oot will interpret any conceivable piece of code. Rather, after reading this tutorial, you will have seen every construct in the language. When you read Oot source code, you'll never have to see some obscure syntax and think, "What does that mean- could that be a language construct that I haven't heard about know yet?".

It's true that Oot isn't as simple as some language, for example, Lisp, or Nock (for some Lisps, [an "all of lisp" could fit in http://lib.store.yahoo.net/lib/paulgraham/jmc.ps 13 pages], and "all of Nock" fits on one page!). But we think that this tutorial is still small enough to fit in your head.

todo

See also Oot.

(note: https://www.fpcomplete.com/blog/2012/09/ten-things-you-should-know-about-haskell-syntax provides an intro to haskell, including gotchas for ppl from popular languages into ML-syntax-style languages, might want to read thru it to find gotchas for Oot syntax coming from other languages)

todo: twitter clone using SQLite