CSE-321 Programming Languages - Assignments

[ Home | Schedule | Assignments | Software | Resources ] gla@postech Sungwoo Park

Words on academic integrity

  • Be sure to read the document on the disciplinary policy for this course. [PDF]
  • You should never post code relevant to assignments to the discussion board.
  • Your code will be compared with other students' code by a code-checking program.
  • Do not try to outsmart the teaching staff with some, perhaps ingenious, tricks. Instead invest your time in the assignment!

Programming assignments

  • Your code should strictly follow the Standard ML style guide for this course.
  • You should hand in your assignment electronically before the due date. After the due date, the hand-in directory will be closed and you will NOT be able to access it. No late submissions will be accepted.
  • Grading criteria:
    • Correctness: Your program should satisfy the given specification.
    • Clarity: Your program should be easy to read, with enough documentation to help readers understand the implmentation. (But beware of unnecessarily long and useless comments!) If we fail to understand your code, you may not receive full credit for your assignment even if it works correctly.
  • Grading criteria NOT applied to programming assignments:
    • Efficiency: You should strive only for the elegance, but never for the efficiency of your code (unless otherwise instructed). In particular, try to avoid using mutuable references or arrays whenever possible so that your code remains pure. You will often be tempted to exploit them in your code, but none of our assignments are designed so as to encourage their use. It is even safe to assume that if your code is not pure, you have not thought enough about the assignment!
  • Your hand-in directory is /afs/postech.ac.kr/class/cse/cs321/handin/.
  • Advice:
    1. Start your assignment early. Keep in mind that the hand-in directory will be closed after the due date.
    2. Spend enough time designing your code before you jump into coding. In other words, think about the problem before typing anything on your screen. It is not uncommon to see that a well-designed specification automatically writes code for you.
    3. Take advantage of the office hours of the teaching staff - they are more than willing to help you.
   Out    Points    Assignment    Due      Solution

1    Thur Mar 4   100 (P) SML Programming (I) [PDF]
  Mar 11 by 11:59pm   hw1-test-fn.sml
2    Thur Mar 11   100 (P) SML Programming (II) [PDF]
  Mar 18 by 11:59pm   hw2-test-fn.sml
3    Thur Mar 19   100 (P) SML Programming (III) [PDF]
  Mar 25 by 11:59pm   hw3-test-fn.sml
4    Thur Mar 25   100 (P) Implementing the λ-calculus [PDF]
  Apr 8 by 11:59pm   hw4-test-fn.sml
5    Thur Apr 8   100 (P) Typechecking the simply-typed λ-calculus [PDF]
  April 15 by 11:59pm   hw5-test-fn.sml
6    Thur Apr 22   100 (P) De Bruijn indexes [PDF]
  May 6 by 11:59pm   hw6-test-fn.sml
  eval-sol.sml (include this file in the sources.cm file)
7    Thur May 6   100 (P) Featherweight Java [PDF]
  May 13 by 11:59pm   hw7-sol.zip
8    Thur May 13   200 + EC (P) Type reconstruction and translation
  June 10 by 11:59pm

P = Programming, W = Written, (points) = Extra-credit

[ Home | Schedule | Assignments | Software | Resources ] gla@postech Sungwoo Park