Languages, Compilers and Interpreters
Take historical note of textile and steel industries:— Ras Bodik, re “why learn about compilers”
do you want to build machines and tools,
or do you want to operate those machines?
Most programmers learn languages, whereas most computer scientists learn about languages.
This gives the computer scientist a distinct advantage over the programmer, even in the domain of programming! Their knowledge generalizes; they are able to understand the operation of a new language more deeply and expeditiously than those who have merely learnt specific languages.
The course is scoped to give software engineers a first look under the covers of popular languages and their implementations. Compared to a typical compilers course, some of the details of compiler design are treated summarily, so as to afford more time building a stronger understanding of the general design of languages and operation of compilers and interpreters.
- Overview and History
- Lexical Analysis and FSAs
- Parsing Algorithms
- Semantic Analysis and Type Checking
- Stack-based Virtual Machines
- Code Generation and Just-in-time Compilation
- Optimization and Tradeoffs
- Runtime Environments, Stack Management and Garbage Collection
- Language Design Considerations and Applications
Projects and exercises
This course assumes confident programming ability in any language. Familiarity with computer architecture is also advantageous.
Schedule and price
This course will next run twice a week for 4 weeks in July. The total price is $1,800.Apply now Still have questions? Contact us.
Designing and implementing a programming language was one of the most edifying projects I've taken on yet, for more than just the stronger abstract model of computation I learned. Writing such a rich system strengthened every practical intuition I have as a software engineer, and reified my understanding of software as an end-to-end product.
I studied compilers at Bradfield and enjoyed it immensely, because the subject is at once very theoretical and very practical. I now understand why programming languages look and behave the way they do. Also, after implementing parts of a compiler, I am more proficient with data structures and algorithms, particularly trees and recursion. In short, studying compilers will make you a better programmer.
After learning about languages and compilers with Bradfield, I feel like I have a massive head start in weighing and learning new languages. A language like Golang isn’t a complete black box to me any more; it’s statically typed, compiled, garbage-collected, and concurrency-enabled. Knowing how each of these aspects affect the programming experience gives me a grasp on large pieces of the language before even looking at its syntax.