From e55b063cf5d2955b6f69c121f5b13c78461b8247 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Thu, 21 Jul 2016 22:30:20 -0400 Subject: [PATCH] Added doc class --- docs/Writing-the-Cyclone-Scheme-Compiler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Writing-the-Cyclone-Scheme-Compiler.md b/docs/Writing-the-Cyclone-Scheme-Compiler.md index 35c999ac..20161728 100644 --- a/docs/Writing-the-Cyclone-Scheme-Compiler.md +++ b/docs/Writing-the-Cyclone-Scheme-Compiler.md @@ -31,7 +31,7 @@ In addition, developing [Husk Scheme](http://justinethier.github.io/husk-scheme) Cyclone has a similar architecture to other modern compilers: -flowchart of cyclone compiler +flowchart of cyclone compiler First, an input file containing Scheme code is received on the command line and loaded into an abstract syntax tree (AST) by Cyclone's parser. From there a series of source-to-source transformations are performed on the AST to expand macros, perform optimizations, and make the code easier to compile to C. These intermediate representations (IR) can be printed out in a readable format to aid debugging. The final AST is then output as a `.c` file and the C compiler is invoked to create the final executable or object file.