Today we are going to write a compiler together this compiler is going to be the smallest compiler in the world. Since it's going to be a long article you can skip directly to the code if you can't wait 😅.
\nCompilers are there everywhere, right from the point you switch ON your machine till you surf the web or open any application. So why do many developers tend to give less importance to it and don't have much knowledge on how it works 🤔. Probably they think compilers are too scary 👻 and only the nerdiest of the geeks 🤓 can work on it. But that not true. Compilers are quite simple. It's just that they involve a little understanding.
\nBefore jumping into what is a compiler and how compilers work. I'll explain what we are going to do in this article. We are going to write a code to compile a LISP like function calls into C-like function calls. For those of you who don't know what is LISP, it's just a very old programming language like Fortran.
For example if we have two functions add and subtract they would be written like this in LISP and C.
| \n | LISP | \nC | \n
|---|---|---|
| 2 + 2 | \n(add 2 2) | \nadd(2, 2) | \n
| 4 - 2 | \n(subtract 4 2) | \nsubtract(4, 2) | \n
| 2 + (4 - 2) | \n(add 2 (subtract 4 2)) | \nadd(2, subtract(4, 2)) | \n
Easy-pezzy right?
\nOK good!! we will be using the above example as the input for our compiler.
\nSo the compiler is a tool that just converts code from one programming language into another programming language without changing the actual meaning of the code. There is also something called a transpiler you may have come across while building JS application with typescript. A transpiler is also a compiler. So the difference between a compiler and a transpiler is that compiler converts code from a programming language to byte codes which humans can't understand. Whereas a transpiler is a source-to-source compiler i.e it converts code from one language to another and the compiled code is still human-readable.
\nMost of the compilers have three stages on a high level design i.e Parsing, Transformation and Code Generation.
Parsing is basically taking the code we are about to compile and turning it into an abstract representation.Transformation is taking the output from the parsing stage and do whatever changes the compiler wants to do for the abstract representation.Code Generation takes the output of transformation stage and converts it to the new Code.Thats it these are the three main stages of a compiler. 😃
\nAgain parsing can be broken down into two phases Lexical Analysis and Syntactic Analysis.
Lexical Analysis takes the raw code and splits into token with the help of tokenizer also called as the lexer.
For the following code
\n(add 2 (subtract 4 2))The below token structure will be generated
\n[\n { type: 'paren', value: '(' },\n { type: 'name', value: 'add' },\n { type: 'number', value: '2' },\n { type: 'paren', value: '(' },\n { type: 'name', value: 'subtract' },\n { type: 'number', value: '4' },\n { type: 'number', value: '2' },\n { type: 'paren', value: ')' },\n { type: 'paren', value: ')' },\n]Below is the code of how a tokenizer generates the tokens.
\n/**\n* ============================================================================\n* (/^▽^)/\n* THE TOKENIZER!\n* ============================================================================\n*/\n\n/**\n* the tokenizer is going to take the code and covert it to an array of tokens\n*\n* (add 2 (subtract 4 2)) => [{ type: 'paren', value: '(' }, { type: 'name', value: 'add'} ...]\n*/\nfunction tokenizer(input) {\n\n// Let's keep a variable called current that will be used as a cursor.\nlet current = 0;\n\n// Token array for inserting the tokens.\nlet tokens = [];while (current < input.length) {
\n// Take the current character\nlet char = input[current];\n\n// The first thing we want to check for is an open parenthesis. This will\n// later we will use this for `CallExpression`. As of now we will only take care\n// of the character. if we come across one we push them in the token array with type\nif (char === '(') {\n tokens.push({ type: 'paren', value: '(' });\n\n // Then we increment `current` and continue to the next cycle of the loop\n current++;\n continue;\n}\n\n// Next we're going to check for a closing parenthesis. We do the same exact\n// thing as before.\nif (char === ')') {\n tokens.push({ type: 'paren',value: ')', });\n current++;\n continue;\n}\n\n// Let's check for whitespaces. We need them because whitespace exists to\n// separate characters, but it isn't actually important for us to store as a token.\n// We would only throw it out later.\nlet WHITESPACE = /\\s/;\nif (WHITESPACE.test(char)) {\n current++;\n continue;\n}\n\n// Next let us take care of number tokens. It's a bit different because a number can\n// have a continuous sequence and we need to capture the entire sequence of characters\n// as one token.\n//\n// (add 123 456)\n// ^^^ ^^^\n// Only two separate tokens\n//\n// So we start this off when we encounter the first number in a sequence.\nlet NUMBERS = /[0-9]/;\nif (NUMBERS.test(char)) {\n // We're going to create a `value` string that we are going to push\n // characters to.\n let value = '';\n\n // Loop through the characters in the sequence until we encounter a character that\n // is not a number. Push each character that is a number to our `value` and\n // incrementing `current` as we go.\n while (NUMBERS.test(char)) {\n value += char;\n char = input[++current];\n }\n\n tokens.push({ type: 'number', value });\n continue;\n}\n\n// So what about strings then we need to parse the strings as well right. So how do we\n// do it 🤷♀️. You guessed it right we need to look for the start and end of a double quote.\n//\n// (concat \"foo\" \"bar\")\n// ^^^ ^^^ string tokens\n//\n// The same logic can be applied which we used for numbers numberWe'll start by\n// checking for the opening quote:\nif (char === '\"') {\n // value variable to insert the characters to form the string.\n let value = '';\n char = input[++current];\n\n while (char !== '\"') {\n value += char;\n char = input[++current];\n }\n\n char = input[++current];\n tokens.push({ type: 'string', value });\n continue;\n}\n\n// Lastly let's take care of the `name token`. Names are sequence of letters,\n// that are the names of functions in our lisp syntax.\n//\n// (add 2 4)\n// ^^^\n// Name token\n//\nlet LETTERS = /[a-z]/i;\nif (LETTERS.test(char)) {\n let value = '';\n\n // Again we're just going to loop through all the letters pushing them to\n // a value.\n while (LETTERS.test(char)) {\n value += char;\n char = input[++current];\n }\n\n tokens.push({ type: 'name', value });\n continue;\n}\n\n// Finally if we have not matched any characters then let's throw the below error\n// and completely exit.\nthrow new TypeError('I\\'m not really sure what this character is : ' + char);}
\n// Then at the end of our tokenizer we simply return the tokens array.\nreturn tokens;\n}
// export the tokenizer module final compiler...\nmodule.exports = tokenizer;
\n`Syntactic Analysis` takes the token and reformats them into a tree-like structure called `Abstract Syntax Tree or AST` that describes the token's relationship with one another. This is also called as Intermediate representation or AST.\n\nBelow is what an AST looks like{\ntype: 'Program',\nbody: [{\ntype: 'CallExpression',\nname: 'add',\nparams: [{\ntype: 'NumberLiteral',\nvalue: '2',\n}, {\ntype: 'CallExpression',\nname: 'subtract',\nparams: [{\ntype: 'NumberLiteral',\nvalue: '4',\n}, {\ntype: 'NumberLiteral',\nvalue: '2',\n}]\n}]\n}]\n}
\nThe code below is how the parser generates the `AST` by taking the output from the tokenizer as input.\n\n```javascript\n/**\n * ============================================================================\n* ヽ/❀o ل͜ o\\ﾉ\n* THE PARSER!!!\n* ============================================================================\n*/\n\n/**\n* For our parser take the token array from the output of tokenizer and tranform it to AST\n*\n* [{ type: 'paren', value: '(' }, { type:'name', value: 'add'} ...] => { type: 'Program', body: [...] }\n*/\n\n// Let's start by defining a function called parser that accepts an array of token\nfunction parser(tokens) {\n\n // Let's keep a variable called current that will be used as a cursor.\n let current = 0;\n\n // But this time we're going to use recursion instead of a `while` loop. So we\n // define a `walk` function.\n function walk() {\n\n // Inside this function let's start by taking the value of the current token\n let token = tokens[current];\n\n // Let's spilt the each type of token into different nodes\n // starting off with `number` tokens.\n //\n // We test to see if we have a `number` token.\n if (token.type === 'number') {\n // If we have one, we'll increment `current`.\n current++;\n\n // Return a new AST node called `NumberLiteral` and set value to the\n // value of our token.\n return { type: 'NumberLiteral', value: token.value };\n }\n\n // Again let's do the same for a `StringLiteral` node.\n if (token.type === 'string') {\n current++;\n\n return { type: 'StringLiteral', value: token.value };\n }\n\n // Next we're going to look for CallExpressions. We start this off when we\n // encounter an open parenthesis.\n if ( token.type === 'paren' && token.value === '(' ) {\n\n // We'll increment `current` to skip the parenthesis since we don't care\n // about it in our AST.\n token = tokens[++current];\n\n // we will create a node with the type `CallExpression`, and we're going\n // to set the name as the current token's value since the next token after\n // the open parenthesis is the name of the function.\n let node = {\n type: 'CallExpression',\n name: token.value,\n params: [],\n };\n\n // We increment `current` *again* to skip the name token.\n token = tokens[++current];\n\n // Next we would like to add each token as `params` for the `CallExpression` till we\n // encounter a closing params.\n //\n // For this let's make use of Recursion instead of infinitely looping on each result.\n //\n // To explain this let's look at the LISP snippet below which includes multiple paranthesis.\n //\n // (add 2 (subtract 4 2))\n //\n // The token array will have multiple nested paranthesis as well\n //\n // [\n // { type: 'paren', value: '(' },\n // { type: 'name', value: 'add' },\n // { type: 'number', value: '2' },\n // { type: 'paren', value: '(' },\n // { type: 'name', value: 'subtract' },\n // { type: 'number', value: '4' },\n // { type: 'number', value: '2' },\n // { type: 'paren', value: ')' }, <<< Closing parenthesis\n // { type: 'paren', value: ')' }, <<< Closing parenthesis\n // ]\n //\n // We're going to rely on the nested `walk` function to increment our\n // `current` variable past any nested `CallExpression`.\n\n // So we create a `while` loop that will continue until it encounters a\n // token with a `type` of `'paren'` and a `value` of a closing\n // parenthesis.\n while (\n (token.type !== 'paren') ||\n (token.type === 'paren' && token.value !== ')')\n ) {\n // we'll call the `walk` function which will return a `node` and we'll\n // push it into our `node.params`.\n node.params.push(walk());\n token = tokens[current];\n }\n\n // Finally we will increment `current` one last time to skip the closing\n // parenthesis.\n current++;\n\n // And return the node.\n return node;\n }\n\n // Again, if we haven't recognized the token type by now we're going to\n // throw an error.\n throw new TypeError(token.type);\n }\n\n // Now, we're going to create our AST which will have a root which is a\n // `Program` node.\n let ast = {\n type: 'Program',\n body: [],\n };\n\n // And we're going to kickstart our `walk` function, pushing nodes to our\n // `ast.body` array.\n //\n // The reason we are doing this inside a loop is because our program can have\n // `CallExpression` after one another instead of being nested.\n //\n // (add 2 2)\n // (subtract 4 2)\n //\n while (current < tokens.length) {\n ast.body.push(walk());\n }\n\n // At the end of our parser we'll return the AST.\n return ast;\n}\n\n// Just exporting our parser to be used in the final compiler...\nmodule.exports = parser;The next stage of the compiler is the transforamtion stage. In this stage we take the AST from the previous step and do manipulation over it or create a new AST from the existing AST. It can manipulate the AST in the same language or it can translate it to an entirelly different language.
Now let's start transforming our AST.
If we look at the AST closely we have node with a certain property each of these nodes are know as AST node. These nodes define an isolated part of the tree.
For instance for \"NumberLiteral\" we have a node.
\n{\n type: 'NumberLiteral',\n value: '2',\n}and if we conider a \"CallExpression\" then we have the node as
\n{\n type: 'CallExpression',\n name: 'subtract',\n params: [\n // nested nodes\n ],\n}When we are taversing the AST we either add, remove or manipulate the nodes or we can create a new AST from the existing AST.
Since we are targetting a new language let's create a new AST while keeping the old one as reference.
\nTraversal: This process involves visiting all the nodes in the AST with depth-first approach. Comsider the AST{\n type: 'Program',\n body: [{\n type: 'CallExpression',\n name: 'add',\n params: [{\n type: 'NumberLiteral',\n value: '2'\n }, {\n type: 'CallExpression',\n name: 'subtract',\n params: [{\n type: 'NumberLiteral',\n value: '4'\n }, {\n type: 'NumberLiteral',\n value: '2'\n }]\n }]\n }]\n}So for the AST above we would go like:
If we are going to manipulate the nodes directly we would likely to introduce lot of scenarios, so we better we visit each nodes.
\nVistors: So visitor is going to be an object that will have methods to handle different node types.var visitor = {\n NumberLiteral() {},\n CallExpression() {},\n}Whenever we find a match with AST node and visitor object type we will call the methods in the visitor object.
\nInorder to make things simple and to keep track of the modified node let's pass the node and reference to the parent node.
\nvar visitor = {\n NumberLiteral(node, parent) {},\n CallExpression(node, parent) {},\n}Okk so there is a teeny weeny problem with that structure 😑. Imagine we go down the tree of a node as soon as we finish up at the bottom of that node we may endup calling an exit function which may lead to ignoring of other nodes.
\nIn order to support this the final form of our visitor should look like.
\nvar visitor = {\n NumberLiteral: {\n enter(node, parent) {},\n exit(node, parent) {},\n },\n}Looks good now. Now lets write the snippet for our traverser.
\n/**\n* ============================================================================\n* ⌒(❀>◞౪◟<❀)⌒\n* THE TRAVERSER!!!\n* ============================================================================\n*/\n\n/**\n* So our traverser function will accept an AST and also a visior node this visitor\n* node method will be used for performing a mapping with the AST nodes.\n*\n* traverse(ast, {\n* Program: (node, parent) => {\n* //do something here\n* },\n*\n* CallExpression: (node, parent) => {\n* //do something here\n* },\n*\n* NumberLiteral: (node, parent) => {\n* //do something here\n* },\n* });\n*/\nfunction traverser(ast, visitor) {\n // Iterates over the array and call the next function traverseNode with reference\n // to the parent.\n function traverseArray(array, parent) {\n array.forEach(child => {\n traverseNode(child, parent)\n })\n }\n\n // accepts a node and parent so that it can pass both to our visitor methods\n function traverseNode(node, parent) {\n // We start by testing for the existence of a method on the visitor with a\n // matching `type`.\n let methods = visitor[node.type]\n\n // If there is an `enter` method for this node type we'll call it with the\n // `node` and its `parent`.\n if (methods && methods.enter) {\n methods.enter(node, parent)\n }\n\n // Next we are going to split things up by the current node type.\n switch (node.type) {\n // Let's start with the 'Program' array and then call the traverseArray\n // method for the body node\n case \"Program\":\n traverseArray(node.body, node)\n break\n\n // Next we take care of 'CallExpression' since 'CallExpressions' have params\n // we will pass that as the array params.\n case \"CallExpression\":\n traverseArray(node.params, node)\n break\n\n // `NumberLiteral` and `StringLiteral` We don't have anything to do so we just break\n case \"NumberLiteral\":\n case \"StringLiteral\":\n break\n\n // If node type is not recognized we simply throw an error\n default:\n throw new TypeError(node.type)\n }\n\n // if `exit` method is encountered for this node type we'll call it with the\n // `node` and its `parent`.\n if (methods && methods.exit) {\n methods.exit(node, parent)\n }\n }\n\n // Let's call the traverserNode function with the parent parameter as null\n // because the top level does not have a parent\n traverseNode(ast, null)\n}\n\n// exporting the traverser method\nmodule.exports = traverserNext up let's write the transformer function.
\nvar traverser = require(\"./traverser\")\n\n/**\n* ============================================================================\n* ⁽(◍˃̵͈̑ᴗ˂̵͈̑)⁽\n* THE TRANSFORMER!!!\n* ============================================================================\n*/\n\n/**\n* Our transformer is going to take the ast and pass it to the traverser and for\n* the new AST.\n*\n* ----------------------------------------------------------------------------\n* Original AST | Transformed AST\n* ----------------------------------------------------------------------------\n* { | {\n* type: 'Program', | type: 'Program',\n* body: [{ | body: [{\n* type: 'CallExpression', | type: 'ExpressionStatement',\n* name: 'add', | expression: {\n* params: [{ | type: 'CallExpression',\n* type: 'NumberLiteral', | callee: {\n* value: '2' | type: 'Identifier',\n* }, { | name: 'add'\n* type: 'CallExpression', | },\n* name: 'subtract', | arguments: [{\n* params: [{ | type: 'NumberLiteral',\n* type: 'NumberLiteral', | value: '2'\n* value: '4' | }, {\n* }, { | type: 'CallExpression',\n* type: 'NumberLiteral', | callee: {\n* value: '2' | type: 'Identifier',\n* }] | name: 'subtract'\n* }] | },\n* }] | arguments: [{\n* } | type: 'NumberLiteral',\n* | value: '4'\n* ---------------------------------- | }, {\n* | type: 'NumberLiteral',\n* | value: '2'\n* | }]\n* (sorry the other one is longer 😜) | }\n* | }\n* | }]\n* | }\n* ----------------------------------------------------------------------------\n*/\n\n// Transformer function with the ast as params\nfunction transformer(ast) {\n // A new AST with initalization\n let newAst = {\n type: \"Program\",\n body: [],\n }\n\n // We are going to pass a property called context to the node which keeps the reference\n // to the parent\n ast._context = newAst.body\n\n // Let's call the traverser function with ast and our visitor\n traverser(ast, {\n // Take care of NumberLiteral\n NumberLiteral: {\n // We'll visit them on enter.\n enter(node, parent) {\n // create a node call 'NumberLiteral' that will push the parent context.\n parent._context.push({\n type: \"NumberLiteral\",\n value: node.value,\n })\n },\n },\n\n // Let's do the same for `StringLiteral`\n StringLiteral: {\n enter(node, parent) {\n parent._context.push({\n type: \"StringLiteral\",\n value: node.value,\n })\n },\n },\n\n // So `CallExpression` should be taken care like this.\n CallExpression: {\n enter(node, parent) {\n // create a `CallExpression` node with a nested `Identifier`.\n let expression = {\n type: \"CallExpression\",\n callee: {\n type: \"Identifier\",\n name: node.name,\n },\n arguments: [],\n }\n\n // Let's create a new context for the original 'CallExpression' so that we can push\n // arguments\n node._context = expression.arguments\n\n // Ceck the parent node is a `CallExpression` if it is not then\n if (parent.type !== \"CallExpression\") {\n // wrap our `CallExpression` node with an `ExpressionStatement`.\n // This is done because the top level `CallExpression` in JavaScript are actually\n // statements.\n expression = {\n type: \"ExpressionStatement\",\n expression: expression,\n }\n }\n\n // Lat but not the least wrap the expression with the parent context\n parent._context.push(expression)\n },\n },\n })\n\n // return the new AST\n return newAst\n}\n\n// export transformer\nmodule.exports = transformerThis is the final step in our compiler design this phase is going to generate the code for the new program by taking the AST. At times compilers do things that will overlap with the transformation.
\nCode generators work in different ways, some will reuse the tokens from the earlier and others will generate the code in a linear fashion by generating a new AST.
\nIn our code generator we are going to use the same AST and generate our code.
\n/**\n* ============================================================================\n* ヾ（〃＾∇＾）ﾉ♪\n* THE CODE GENERATOR!!!!\n* ============================================================================\n*/\n\n/**\n* Our CodeGenerator is going to call itself recursively to to print a string\n* The code generator is quite straight forward to understand\n*/\n\nfunction codeGenerator(node) {\n // We'll break things down by the `type` of the `node`.\n switch (node.type) {\n case \"Program\":\n return node.body.map(codeGenerator).join(\"\\n\")\n\n // For `ExpressionStatement` call the codegenerator function and add a semicolon\n case \"ExpressionStatement\":\n return codeGenerator(node.expression) + \";\"\n\n // For `CallExpression` we will print the `callee`, and call the codeGenerator\n // recursively so that the end result of recursion is going to be a string\n // the arguments are concatenated as shown below\n case \"CallExpression\":\n return (\n codeGenerator(node.callee) +\n \"(\" +\n node.arguments.map(codeGenerator).join(\", \") +\n \")\"\n )\n\n // For identifier we will return the name\n case \"Identifier\":\n return node.name\n\n // For `NumberLiteral` let's return the value\n case \"NumberLiteral\":\n return node.value\n\n // For `StringLiteral` we just add quotes arround the value\n case \"StringLiteral\":\n return '\"' + node.value + '\"'\n\n // And if we haven't recognized the node, we'll throw an error.\n default:\n throw new TypeError(node.type)\n }\n}\n\n// export code generator\nmodule.exports = codeGeneratorThat's it we are done with our compiler 👏👏👏.
\nFor the last part let us call the compiler program in a file.
\nvar tokenizer = require(\"./tokenizer\")\nvar parser = require(\"./parser\")\nvar transformer = require(\"./transformer\")\nvar codeGenerator = require(\"./code-generator\")\n\n/**\n* ============================================================================\n* (۶* ‘ヮ’)۶”\n* !!!!!!!!THE COMPILER!!!!!!!!\n* ============================================================================\n*/\nfunction compiler(input) {\n let tokens = tokenizer(input)\n let ast = parser(tokens)\n let newAst = transformer(ast)\n let output = codeGenerator(newAst)\n\n // and simply return the output!\n return output\n}\n\nmodule.exports = compiler