If you are bold enough to use the Korn shell, we applaud your choice and assume you can manage PATH=~cs152/bin:$PATH.
cat solution mytests | impcore -qDon't include test cases in the solution file you submit.
You may find it more convenient to keep solutions in separate files as you develop them. If so, we recommend that you do so and combine them in the end with cat, and that you use Make to manage the combination. For example, you could try something like this in a Makefile:COMPONENTS=s1 s2 s3 s4 s5 s6 solution: $(COMPONENTS) cat $(COMPONENTS) > solution submit: solution submit-intro test: solution mytests cat solution mytests | impcore -q(Be aware that we have not tested such a Makefile.)
;; ;; Problem N ;;
Turn in your answer on paper.
Programming-language proofs are probably unfamiliar, so you may want to look at some sample cases we have provided to help you. Also, to relieve some of the tedium (which is very common in programming-language proofs), we suggest that you allow your proof for the AddApply case to stand in for all other cases involving primitive operators. We also suggest that you simplify by leaving out the global environment xi.
Turn in your answer on paper.
patch < impcore-local-diffs
-> (define gcd (n m) (r) ... more code for gcd ... ) -> (gcd 48 30) 6For every test case you submit, and for every interpreter another student submits that your test cases exposes a bug in, we will give you a point. For every test case that exposes a bug in the course software, we will give you at least 5 points (maybe more, depending on our judgment of the severity of the bug).