11#lang scribble/manual
2- @title[#:tag "Assignment 2 " #:style 'unnumbered ]{Assignment 2: Racket Primer}
2+ @title[#:tag "Assignment 2 " #:style 'unnumbered ]{Assignment 2: a86 Primer}
33
4- @bold{Due: Wednesday, September 13 , 11:59PM}
4+ @bold{Due: Wednesday, February 14 , 11:59PM}
55
6- The goal of this assignment is to gain practice programming in Racket .
6+ The goal of this assignment is to gain practice programming in a86 .
77
88@bold{This is a collaborative assignment.} You may work with anyone
99you'd like on this assignment, but each person must submit their
10- @tt{main.rkt} file on Gradescope.
11-
12- You are given a @tt{main.rkt} file (on ELMS under "Files " ), that
13- contains a number of sections. In each section there are several
14- function ``stubs,'' i.e. incomplete function definitions with type
15- signatures, descriptions, and a small set of tests. Each function has
16- a bogus (but type correct) body marked with a ``TODO'' comment. Your
17- job is to replace each of these expressions with a correct
18- implementation of the function.
19-
20- The last section of problems deals with functions that operate over a
21- representation of expressions in a lambda-calculus-like language and
22- asks you to compute a few simple facts about the given expression.
23-
24- Make sure you do not rename the file. Also make sure not to change
25- the name or signature of any function given to you. You may add any
10+ @tt{submit.zip} file on Gradescope.
11+
12+ You are given a @tt{a86-basics.zip} file (on ELMS under "Files " ), that
13+ contains a README, a Makefile, and a number of Racket modules. In
14+ each module there are several ``stubs,'' i.e. incomplete definitions
15+ with type signatures, descriptions, and a small set of tests. Each
16+ definition has a bogus (but type correct) body marked with a ``TODO''
17+ comment. Your job is to replace each of these expressions with a
18+ correct implementation of the a86 code.
19+
20+ Make sure you do not rename any files. Also make sure not to change
21+ the name or signature of any definition given to you. You may add any
2622additional functions that help you solve the overall problem you're
2723tackling.
2824
@@ -37,15 +33,19 @@ You can test your code in several ways:
3733 This is actually a configurable preference, but it is on by
3834 default.}
3935
40- @item{Using the command line @tt{raco test main.rkt} from
41- the same directory as @tt{main.rkt}.}]
36+ @item{Using the command line @tt{raco test <filename.rkt>} from
37+ the same directory as your Racket code will test the module
38+ in @tt{<filename.rkt>}. If you run @tt{raco test .}, it will
39+ test all of the Racket files in the current directory.}]
4240
43- Note that running @tt{racket main .rkt} from the command line will
44- @bold{not} run the tests .
41+ Note: running @tt{racket <filename .rkt>} will @bold{not} test the
42+ file ; you need to use @tt{raco} or DrRacket .
4543
4644@section[#:tag-prefix "a2- " #:style 'unnumbered ]{Submitting}
4745
48- Submit your filled-in @tt{main.rkt} file on Gradescope.
46+ Use the included Makefile to run @tt{make submit.zip} (or simply
47+ @tt{make}) to generate an appropriate @tt{submit.zip} file for
48+ submitting to Gradescope.
4949
5050@section[#:tag-prefix "a2- " #:style 'unnumbered ]{Grading}
5151
0 commit comments