dkalaxdk / p4

Compiler for the Language EBAL

P4: EBAL

Project description:

This project is developed as a semester project on the fourth semester on AAU. The goal of the project was to design a language, and implement a corresponding compiler for the language.

The result is a compiler, built around the principles of Crafting a Compiler, ISBN-13: 978-0136067054 and the courses of the semester.

The language designed in this semester is an event based Arduino language, called EBAL, which goal is to abstract away as many details as possible regarding the communication between multiple Arduino boards. The aim is to help with making home automation easier, and to remove the boilerplate code.

The communication works by having one Master board, containing the input pins that needs to be monitored, and one or more slave boards, containing the output pins of the system.

How to use:

The project can be compiled using any java compiler. Code written in EBAL can be seen in TestFiles/CompilerTest.txt.

After compilation, the output code needs to be compiled using an Arduino IDE or compiler. The compiled code utilises a library which can be found in EBAL.Zip.
When installing the library to the Arduino IDE, follow this guide: Arduino library installation. When this is done the output code from the compiler can be run as any other Arduino code.

The output of the EBAL compiler will be multiple files, a file for the Master board, and one for each slave.
These needs to be compiled in the Arduino IDE one by one, and then be put on the respective Arduino boards. When compiling the files through the Arduino IDE, each file needs to be added to a folder with the same name of the output file.

General code overview:

The compiler is implemented using a recursive descent parser, as the designed language is LL(1).

EBAL was designed and implemented as a semester project, and is therefore not fully implemented. The language does not contain any iterative control structures, arrays or strings, nor does it contain a way for the slaves to communicate with the master board.

p4's Issues

Scanner

• Regular Expressions
• Switch case?
• DFA?

Beskriv Scanner design

Preprocessor

fx til fjerne kommentarer

Parser

• Lav AST?

Language design

Beskriv Semantics

Definer indbyggede funktioner (Hvad gør broadcast etc)

Type Rules

Hvordan må typerne bruges? Nok mere under semantics

Konverter CFG i rapport til EBNF

Problemformulering

Criteria

Program eksempler/Test af kopling af Arduinoer

Compiler Design

Arduino, what is?

AST Design

Hvordan har vi designet AST'en?

Introduction

Declarative programming

Beskriv Unit Tests

Skriv afsnit om Unit Testing i rapporten

Scope Rules

Hvordan fungerer vores scopes?

Scanner implementeringsafsnit

Analyser forskellig Arduino sproget

Symbol Table (semantic analysis)

Argumenter for hvorfor vi ikke bruger værktøjer til at lave vores compiler

Beskriv Parser design

Symbol Table Design

Hvilket design vil vi bruge? Hashtables, linked lists, osv.

Fix Criteria

Flyt Criteria ind under Language design som en section, efter Paradigms.

Beskriv Arduino sproget. (loop, setup, osv)

Kun analysere Serial, Wire og Eventually i betragtning som libraries

“Spred” Criteria Focus ud på de andre afsnit, så de hver især konkluderer på hvad vi tager med, og hvorfor de ikke helt er gode nok. Så criteria focus kommer ikke til at eksistere efterfølgende.

Lav evt en summary der er resten af criteria focus

Beskriv syntax (CFG)

Lav et program eksempel med vores eget programmerings sprog

Paradigmer

Sæt grammar pænt op