CPSC 326: Homework Assignment 5 Due: Tuesday, Apr. 4

Goals:

• Develop a better understanding of VM-based stack machines and their use in PL interpretation.

• Implement the MyPL bare-bones VM interpreter.

You are free to use whatever IDE and machine you prefer for this class. However, to complete the assignment, you will need git, g++ (version 11 or higher), cmake, make, the google test framework, and valgrind installed. It can also be useful to have a debugger such as gdb installed as well. Each of these are already installed on the remote development server (ada.gonzaga.edu) provided by the CS Department. However, you may also install these programs on your own machine, via a virtual machine, running WSL2, or on your own remote server. Note that you will also need a GitHub account for obtaining starter code and for submitting your assignment.

Instructions:

1. Use the GitHub Classroom link (posted in Piazza) to copy the starter code into your own repository. Clone the repository in the directory where you will be working on the assignment (e.g., onto ada or your own machine).

2. Finish the VM implementation by filling out the vm.cpp file.

3. Ensure your code passes the unit tests provided in vm_tests.cpp within the tests subdirectory.

4. Finish the implementation of the hw6.cpp program. In particular, you must implement the given MyPL program (given in hw6.cpp) as VM instructions. This will also serve as a test of your VM implementation.

5. Create a short write up as a pdf file named hw6-writeup.pdf. For this assignment, your write up should provide a short description of any challenges and/or issues you faced in finishing the assignment and how you addressed them along with evidence (screenshots) that your hw6 program is working correctly. The screenshots should show the running of hw6 with a variety of different inputs. Be sure your hw6-writeup.pdf file is in the main directory of your assignment (and not within the src directory or any other subdirectory).

6. Submit your program. Be sure to add, commit, and push all assignment files to your GitHub repo. You can verify that your work has been submitted via the GitHub page for your repo.

Homework Submission and Grading. Your homework will be graded using the files you have pushed to your GitHub repository. Thus, you must ensure that all of the files needed to compile and run your code have been successfully pushed to your GitHub repo for the assignment. Note that this also includes your homework writeup. This homework assignment is worth a total of 30 points. The points will be allocated according to the following.

1

1. Correct and Complete (24 points). Your homework will be evaluated using a variety of different tests (for most assignments, via unit tests as well as test runs using specific files). Each failed test will result in a loss of 2 points. If 10 or more tests fail, but some tests pass, 4 points (out of the 24) will be awarded as partial credit. Note that all 24 points may be deducted if your code does not compile, large portions of work are missing or incomplete (e.g., stubbed out), and/or the specified techniques, design, or instructions were not followed.

2. Evidence and Quality of Testing (2 points). For each assignment, you must provide additional tests that you used to ensure your program works correctly. Note that for most assignments, a specific set of tests will be requested. A score of 0 is given if no additional tests are provided, 1 if the tests are only partially completed (e.g., missing tests) or the tests provided are of low quality, and 2 if the minimum number of tests are provided and are of sufficient quality.

3. Clean Code (2 points). In this class, “clean code” refers to consistent and proper code formatting (indentation, white space, new lines), use of appropriate comments throughout the code (including file headers), no debugging output, no commented out code, meaningful variable names and helper functions (if allowed), and overall well-organized, efficient, and straightforward code that uses stan- dard coding techniques. In addition, when compiled, your code should not have any warnings. A score of 0 is given if there are major issues, 1 if there are minor issues, and 2 if the “cleanliness” of the code submitted is satisfactory for the assignment.

4. Writeup (2 points). Each assignment will require you to provide a small writeup addressing chal- lenges you faced and how you addressed them as well as an explanation of the tests you developed. Homework writeups do not need to be long, and instead, should be clear and concise. A score of 0 is given if no writeup is provided, 1 if parts are missing, and 2 if the writeup is satisfactory.

2