compiler

Note: Use Joel's compilerFastCheck.sh! Read the instructions. I should have the config set up properly but you'll need to copy the stage0 dat files:

From the compiler directory on csunix:

cp /usr/local/4301/data/stage0 input

Then, while still in the compiler directory:

mkdir output

Once you make stage0 you can run ./compilerFastCheck.sh and it will print all kinds of magical information!

DIFF CHECKLIST

Compiler project for Algorithmic Languages and Compilers — Fall 2022

CS 4301 Jeff Caldwell Kangmin Kim

Lecture references

First look at project

Week 9, October 20, 50:00

Producing two other files

Listing file
Object file
Errors should be printed to listing file and compilation should stop
- Motl says "You should find that first error and stop"
Symbol table entries will be stored as maps
- key will be the name the user has given to the symbol (external name)
- value: internal name, data type, data mode, value, allocation, units
  - Values added during insert statement in progStmt

Womack gave us some scripts!

setup.sh and createData.sh

To run them:

chmod 771 setup.sh
chmod 771 createData.sh

"setup can be ran anywhere and will make a data folder in that directory, createData needs to be moved into the data folder and will create an output file and diffs and whatnot"

"Note that to use to use shell scripts after the chmod they can be activated like:"

./setup.sh

"Note that this does not make a stage0.cpp in the data folder. You need to copy or move one in there before calling createData

Also calling setup again will clean out and remake said data folder"

"Also if your wondering why it says you have diffs and there's no obvious difference, instead of using"

<< "\n"

Do instead 

<< "\r\n"

Notes

The focus of Stage 0 is just the declaration of our data.

We have the benefit of being in very different time zones! One of us can be working on the project at almost all times this weekend.

Check the lecture from November 3, 2022 — Dr. Motl talks about the need to patch something that's not in the pseudocode.

Page 9 of Overall Compiler Structure near the code block:

if (y == "not")
{
if (nextToken() is not a BOOLEAN)
processError(boolean expected after “not”)
if (token == "true")
y = "false"
else
y = "true"
}

He also mentions something about a while loop

Motl says unit will be either 0 or 1