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

Reflecting on what was learned from writing this book

We have learned some useful things from writing this book. Among other things, we concluded that Java is very suitable for writing compilers at this point. Sure, Andrew Appel might have published Modern Compiler Implementation in Java in 1997, and other compiler writing books in Java exist. These might be great, but many compiler writers won't consider using Java if it means giving up lex and YACC. Using a standard lex/YACC toolchain for Java makes it more interoperable with compiler code bases created for other languages.

I want to express my appreciation to the Byacc/J maintainer Tomas Hurka for accepting and improving my static import patch to make Byacc/J play more nicely with Jflex and similar tools (including my Merr tool, as covered in Chapter 4, Parsing) that generate yylex() or yyerror() in separate files. Supporting yylex() and yyerror() in separate files obviates the need for stupid workarounds, such as writing...