Make changes suggested by Ryan
This commit is contained in:
@@ -54,7 +54,7 @@ an alternative way of representing the program that isn't machine code.
|
||||
In some compilers, the stages of parsing and analysis can overlap.
|
||||
In short, just like the pirate's code, it's more of a guideline than a rule.
|
||||
|
||||
#### What we'll cover
|
||||
#### What we will cover
|
||||
We'll go through the stages of a compiler, starting from scratch
|
||||
and building up our project. We'll cover:
|
||||
|
||||
@@ -128,7 +128,7 @@ constructed from an integer and another list (as defined in our `data` example),
|
||||
return the integer".
|
||||
|
||||
That's it for the introduction! In the next post, we'll cover tokenizng, which is
|
||||
the first step in coverting source code into an executable program.
|
||||
the first step in converting source code into an executable program.
|
||||
|
||||
### Navigation
|
||||
Here are the posts that I've written so far for this series:
|
||||
@@ -136,3 +136,4 @@ Here are the posts that I've written so far for this series:
|
||||
* [Tokenizing]({{< relref "01_compiler_tokenizing.md" >}})
|
||||
* [Parsing]({{< relref "02_compiler_parsing.md" >}})
|
||||
* [Typechecking]({{< relref "03_compiler_typechecking.md" >}})
|
||||
* [Small Improvements]({{< relref "04_compiler_improvements.md" >}})
|
||||
|
||||
Reference in New Issue
Block a user