CSC 148H - INTRODUCTION TO COMPUTER SCIENCE

Announcements and Advice about Assignment 2

Wednesday 11 Oct: Sybmit directory

In case there is any confusion, you are to submit the appropriate assignment 2 files to the "A2" folder. (That's with a capitol "A".) Do not put them in a subfolder under A2.

We will start being strict about this for assignment 2.

Wednesday 11 Oct: Memory model - a final snapshot

Your memory model diagram should show only the state of affairs at the moment when the comment "For question 1, trace everything up to this point" is reached. You do not need to show any of the history that leads up to this.

Tuesday 10 Oct: A bunch of stuff re the memory model trace

• You may leave out the names of functions in any instances of ArrayList or CalEntry.
• In the stack of boxes for an object in the object space, you may leave out boxes for things inherited from Java API classes. So if you had an instance of CalEntry, it inherits from Object, but you don't have to show a box for its Object part.
• Use the old names (from the starter code), not your new and improved names, when labelling things in your memory model trace.
• Here's an example of how you can draw an array. In this example, it's an array of 10 integers, and there is a zero in each slot. Because all slots have the same value, it's okay to use dot-dot-dot rather than draw every single slot. I have included a memory address (1101) in case I need to refer to this array somewhere else.

Tuesday 10 Oct: Table of variable name changes

The handout says "To help us find the name changes you've made, fill out the tables that appear in the comments at the top of classes ArrayList and CalEntry" Here is the table to fill out and insert into ArrayList and CalEntry:

// Table of variable name changes:
//
// Old name (in the starter code)      New and improved name
// --------------------------------------------------------------------

Thursday 04 Oct: Testing driver?

The main() method in ArrayList has a comment that says: "You should replace this with a driver that does thorough testing." Ignore this; I meant to delete it. You do not need to do any testing of this program. (You may decide you want to, though, as part of figuring out what the methods do.)

Wednesday 04 Oct: Hint

A good first step would be to figure out the purpose of the instance variables in ArrayList: contents, bool, and num. You'll have to look at the methods to do this, but you won't have to understand every last line to get the idea. Then write down what you figured out as a comment on each variable. (Guess what? That's a representation invariant!) As you understand the code better, you may need to fine tune this invariant, but having the basic idea written down will help you understand the code.

You may be inspired at this point to rename some or all of these variables. Do it now, so you can benefit from the better names as you read the code.

Wednesday 04 Oct: Javadoc

You are not required to use Javadoc for this assignment.