On this page:
Overview
Setup
Tasks
Before Submitting
Submitting

Homework 10🔗

Last updated: Wed, 6 Nov 2024 11:51:38 -0500

Out: Wed Nov 06, 2024, 12pm (noon) EST

Due: Mon Nov 18, 2024, 12pm (noon) EST

Overview🔗

In this assignment, we will continue our deeper study of "high-level languages" by implementing (a basic) one. Fortunately, using the The Design Recipe, this seemingly difficult task can be completed using the exact same methods as previous assignments.

This hw will be graded accordingly:

  • correctness (12 pts)

  • design recipe (24 pts)

  • style (12 pts)

  • README (2 pt)

Total: 50 points

Setup🔗

Create a new repository for this assignment by going to the CS450 Fall 2024 GitHub Organization and clicking "New".

Note: The CS450 Fall 2024 GitHub Organization must be the owner of the repository. Do not create the repository in your own account.

On the "Create a new repository" screen:
  • Name the repository hw<X>-<LASTNAME>-<FIRSTNAME> where <X> is the current homework number.

    For example, I would name my hw10 repository hw10-Chang-Stephen.

  • Mark the repository as Private.

  • Check "Add a README file".

  • Select the Racket template for the .gitignore.

  • Choose whatever you wish for the license.

When done click "Create repository".

Tasks🔗

Reading

Notes and Reminders

Programming

In Lecture 17, Lecture 18, and Homework 9 we created a basic programming language that included JavaScript "add strings" semantics.

In this assignment, we will add booleans and some boolean operations. Specifically, we add a "triple equal" operator (which is analogous to Racket’s equal?) and a "ternary conditional" (which is like Racket’s if expression). We will again follow JavaScript semantics, however, which can be a bit tricky. In particular, you may want to read up on "truthy" values and how they behave. As before, we will use the repljs.com evaluator as the official specification for the behavior of "CS450 Lang" programs.

Specifically, extend the functions from Homework 9 to accommodate the following Data Definition changes. Note that in some instances, the exact data definition is not specified and is left up to you to design.

For reference, here are the Data Definitions that we are using:

Before Submitting🔗

Testing

Before submitting, note:
  • Do not submit until all code has been thoroughly tested (by you).

  • Assignments may or may not use a GradeScope Autograder, but either way, an Autograder is not a software development tool so do not use it as one. Code must be tested independent of any Autograder.

  • If you submit and get an Autograder error, this means the code you wrote is not complete and/or not correct and it’s up to you to figure out why.

  • Of course, the course staff is here and eager to help, but cannot do so if a student does not explain what they’ve tried first (e.g., "why is the Autograder giving an error?" is not something we can help with). At the very least you should report what error you are seeing and which part of the error message you do not understand.

  • The Autograder test suite is subject to change. This means that the visible grade seen during submission is not the final grade.

Style

All code should follow proper Racket Style.

Also, the repository itself must follow proper style. Specifically, it must have appropriate commit messages. See How to Write a Git Commit Message if you are unsure how to write a commit message.

Files

A submission must have the following files in the repository root:

Submitting🔗

When you are done, submit your work to Gradescope hw10. You must use the "GitHub" Submission Method and select your hw<X>-<LASTNAME>-<FIRSTNAME> repository.

Note that this is the only acceptable way to submit homework in this course. (Do not manually upload files and do not email files to the course staff. Homework submitted via any unapproved methods will not be graded.)