02IntermediateJava

02IntermediateJava - CS108 Stanford Winter 2010 Handout#2 Young Intermediate Java Handout written by Nick Parlante This doc gathers miscellaneous

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
CS108, Stanford Handout #2 Winter 2010 Young Intermediate Java Handout written by Nick Parlante This doc gathers miscellaneous intermediate Java topics needed in CS108. Many of these are topics are not given full coverage in an introductory Java course such as CS106A. Assignment 0 : read through this handout once to have familiarity with these topics, as they will all appear somewhere in the CS108 code. We will review a few of the topics here plus Java Generics in the section Thu eve. The first part deals with many little topics: arrays, shallowness, packages, command line java, static variables and methods, file reading, exceptions. The second part concentrates on the Java Collection classes: List, Map, and Set. The 2nd part has different typography, as I'm preparing it in HTML to be published on the web. Pervasive Shallowness in Java / GC In C++, when you use an "=" for assignment, you always wonder how "deep" the copy is. In Java, = is always "shallow" -- copying the pointer but not the object. Suppose we have some Foo class: Foo x = new Foo(1); Foo y = new Foo(2); x = y; // shallow -- just make x point to 2nd Foo, Garbage Collector gets the 1st Foo bar(x); // same, just pass a pointer to the Foo object into bar() The garbage collector (GC) does the deallocation bookkeeping for us, deallocating a heap object when the number of pointers to it goes to zero. "new" allocates, the GC cleans up. It is common in Java to have a few objects and proliferate pointers to those few objects all over the place. Many parts of the program share ownership of the objects. We can afford to have pointers spread all over, since the GC manages the deallocation bookkeeping. This pervasive sharing can be a problem if we want to change an object, since many parts of the program may be pointing to it. Sharing is not a problem if the object is "immutable" -- having no mutating methods so the object never changes once it is constructed. Another solution is to make a copy of the object before changing it. Some classes provides a "copy constructor" (C++ terminology) -- a constructor that takes a pointer to an existing object as an argument, and initializes a new object to be a copy. In general, making copies of things is something more often done in C++ than in Java. I think this is because the GC gives us the freedom to not make copies in many situations. Foo x = new Foo(1); Foo copy = new Foo(x); // make a copy of x (depends on existence of a copy constructor) There is also an old java object copying facility called "Cloneable", but it turned out to be a messy design and has fallen out of favor. I recommend that you never use it. Array Review As a warmup, remember how arrays work in Java: int[] a = new int[100]; // Allocate array in the heap, a points to the array a[0] = 13; a[1] = 26; a.length // read-only access .length -- 100 (not .length(), that's for strings) a[100] = 13; // throws ArrayOutOfBounds exception at runtime
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 "Arrays" Utility Class
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/12/2010 for the course CS 108 taught by Professor Jimenez during the Winter '08 term at Stanford.

Page1 / 10

02IntermediateJava - CS108 Stanford Winter 2010 Handout#2 Young Intermediate Java Handout written by Nick Parlante This doc gathers miscellaneous

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online