Homework 7 (Due 11:59pm Thursday, November 5, 2020)

Submit via SVN


This homework should be done in Full Java (using DrJava, IntelliJ, Eclipse, or a text editor and command line compilation and execution).  The Functional Java language in DrJava regrettably no longer works for more complex OO code such as the visitor pattern.  In this assignment, you will re-implement each of the functions on IntLists assigned in Homework 7 using the visitor pattern.

As before, your program must support the object-oriented formulation of lists of integers defined the composite class hierarchy where

The Homework Support files IntList.java, IntListVisitor.java, LengthVisitor, ScalarProductVisitor, and IntListTest.java provide a starting point for your code.   Feel free to edit these files and omit files that are not needed in this homework assignment.


Apply the visitor design pattern to define visitor classes implementing the IntListVistor interface IntList and its subclasses given above to formulate all of the following methods as  visitorsJUnit test class, IntListTest to test all of your new methods in the IntList class.  Use the LengthVisitor example as a guide for defining your new visitor classes.  Augment the test clas IntListTest.java to include test methods for each of your visitor classes.  Confine your documentation to writing contracts (purpose statements in HTDP terminology) for each visitor using javadoc notation (a comment preceding the corresponding definition) beginning  with /** and closing  with */ for each visitor class.  Use the documentation of LengthVisitor in the Homework Support files as an example.

Testing Tricks

In Racket, the equal? function performs structural equality.  Java does not include such a built-in operation.  For the IntList composite type, we overrode the inherited equals method (trivially defined in class Object) by an equals method that implements structural equality but it is slightly more complex than you might expect.  Recall that the argument passed to equal has type Object.  Hence, we have to worry about the class of the argument; the simple (and IMO best) definition of structural equality is to mandate that objects cannot be equal unless they are instances of the same class.  Study the definition of the equals method in class ConsIntList.  Unfortunately, we can write the body of this method the return of a boolean-valued expression, because Java does not support a notion of local or let at the level of expressions.  So the body is an if statement where explicit return statements in the consequent statement and alternative statement.  Notice that we still programmed in a functional style without any mutation.

To test the computations that yield results of composite type, we can either define structural equality over the composite type (as we did for IntList) or write an intelligible toString method for the composite type (which I strongly recommend for debugging purposes) and compare the toString() representations of the composite type.  But beware that toString() equality may not imply structural equality and vice versa.  You should always endeavor to make them agree.