Book Image

Build Your Own Programming Language

By : Clinton L. Jeffery
Book Image

Build Your Own Programming Language

By: Clinton L. Jeffery

Overview of this book

The need for different types of computer languages is growing rapidly and developers prefer creating domain-specific languages for solving specific application domain problems. Building your own programming language has its advantages. It can be your antidote to the ever-increasing size and complexity of software. In this book, you’ll start with implementing the frontend of a compiler for your language, including a lexical analyzer and parser. The book covers a series of traversals of syntax trees, culminating with code generation for a bytecode virtual machine. Moving ahead, you’ll learn how domain-specific language features are often best represented by operators and functions that are built into the language, rather than library functions. We’ll conclude with how to implement garbage collection, including reference counting and mark-and-sweep garbage collection. Throughout the book, Dr. Jeffery weaves in his experience of building the Unicon programming language to give better context to the concepts where relevant examples are provided in both Unicon and Java so that you can follow the code of your choice of either a very high-level language with advanced features, or a mainstream language. By the end of this book, you’ll be able to build and deploy your own domain-specific languages, capable of compiling and running programs.
Table of Contents (25 chapters)
1
Section 1: Programming Language Frontends
7
Section 2: Syntax Tree Traversals
13
Section 3: Code Generation and Runtime Systems
21
Section 4: Appendix

Integrating a compiler into a programmer's editor

The front half of the Unicon compiler—loosely corresponding to Chapter 2, Programming Language Design, up to Chapter 5, Syntax Trees, in this book—was integrated into the Unicon IDE, known as ui. The Unicon frontend consists of three major components: a preprocessor, a lexical analyzer, and a parser. In the Unicon translator, these components are called from a main() procedure. The translator opens, reads, and writes files in the filesystem to perform its I/O, and provides feedback to the user by writing text to standard output or standard error on a console or terminal window. In an IDE, the compiler components are called from behind the scenes while the user is editing their code in a graphical UI (GUI). The source code is obtained directly from the memory in the IDE and the compiler's output is obtained from the memory by the IDE and presented to the user. Altogether, seven files from the Unicon translator...