21: Building a compiler. Part 2

In full swing building our compiler interpreter. We’ve got our lexer working nicely. Now for the meaty part of it. The process of taking all the source code that is now tokenized, and outputting into a data structure is the job of the parser. This output structure is called a ‘syntax tree’ or ‘abstract syntax tree’, did you checkout last week’s pick?

20: Building a compiler. Part 1

Something I’ve wanted to know more about, having missed out on the usual opportunity during a CS degree, is the process of a compiler. How we get from source code to running byte code on the other end. The process of writing Elm that compiles to JavaScript using a compiler written in Haskell, was the tipping point for me. Compound that with webpack walking the Abstract Syntax Tree, and learning the term ‘lexical scope’ from Kyle Simpson in his YDYJS series.

19: More than Just Functions

The idea of functional programing is more than just the use of functions, or functions as first class citizens. It is a real paradigm shift in the way we think about tackling problems with code. A lot of what brings me, and others, to Elm is the desire to learn and even more importantly use techniques that FP puts forth in our daily programing. While trying to tackle static types, curring, partial application, and a bucket of other important concepts, it’s the idea of FP that brought a lot of us here in the first place, less we forget it.

18: Ports by example

It’s time to dive right in with several uses of Ports in Elm, what better way than by example! Ports are Elms way of interacting with the outside world, currently with JavaScript, but the sky is the limit.