homeworks

Standard instructions for all homeworks:

Your name, the assignment-number, and the URL of this assignment-page must be in a comment at/near the start of the file.
Any code which results in syntax errors will generally not earn more than 50% of the points-possible. For grading, I will ignore any commented-out code (including commented-out tests).
Hardcopy must be stapled (if hardcopy required), if more than one sheet.
Your code must be clear:
- Indent meaningfully.
- Use meaningful function- and variable-names.
  (If a name is mandated in the homework, be sure to use it, spelled correctly.)
- Include a one-sentence purpose-statement for each function.
  E.g. "Return a word that is a linguistic blend of $wrd1 and $wrd2." (A good purpose-statement refers to its parameters by name.)
  For dynamically-typed languages, be sure to also include the parameter and return-types.
  Note that comments inside a function are typically not needed, unless a particular line is there for some non-straightforward reason. You can assume anybody reading your code is a programmer who understands all the language's features.
- Include test cases for every function.
  (Note that you do not need to test, or handle, inputs that don't meet your pre-conditions, including the input-type.)
On returned homework, see general grading guide for any greek-letter codes (e.g. ι (iota) for “indentation”) and proofreader marks. (Or, look at it pre-emptively, for common ways of losing points on programs!)

This page licensed CC-BY 4.0 Ian Barland
Page last generated Please mail any suggestions
(incl. typos, broken links)
to ibarlandradford.edu