COP-4338, Programming III Lectures
Note: Links will not be alive until a day or two before class.
- May 11, 13, and 18: C++ Basics, arrays, strings, files, pointers, reference variables
- Simple C++, and compiling functions
- vector class.
- resizing and push_back
- string class.
- Parameter passing: call by constant reference.
- new and delete
- Reference variables
- May 20 and 25: Classes
- Classes: interfaces, member functions, visibility
- Separation of interface and implementation
- Default parameters
- Scope :: operator
- ifndef/endif and separate compilation
- Const and non-const methods
- Implicit type conversions
- Explicit constructors
- Initializer lists
- Static members
- Operator overloading
- The big three: destructor, operator= and copy constructor
- Constant and reference data member
- Linked data structures
- Aliasing and this
- Example: The Rational class
- Reference return types and operator
- May 27 and June 1: Inheritance
- Implementing a derived class
- Defaults for the Big Three in the derived class
- Protected members
- Static vs. dynamic binding
- virtual keyword
- The virtual destructor
- Various C++ differences from Java
- June 3: Templates
- Why templates
- Function templates
- Class templates: interface
- Illustration of the MemoryCell class
- Specifying the requirements of the template type
- Class templates: implementation
- Separate compilation issues
- A Set class (uncommented):
(the last file is for separate compilation of templates).
- An LSet (linked list version) class (uncommented):
- Function Objects
- Reference return types
- June 8: STL
- Pointer variables and their relation to primitive arrays
- Primitive strings
- STL Basic ideas
- Lists vs Vectors
- The Pair pattern
- Sets and maps
- The concordance example
- String streams
- June 10 and 15: Programming in C
- June 22: Exam #1 C++ and C
- June 17: Java 1.5, The Object class, Reflection, and the Proxy Pattern
- Object class PDF slides
- Reflection PDF slides
- Illustration of the correct way to override
equals, hashcode, toString,
- Illustration of using reflection to invoke main
- Using accessible fields to get private data
- Illustration of the proxy pattern.
Shows generation by hand, generation by using Java 1.3 dynamic proxies,
and an approximation of what
the dynamic proxy is actually producing for you behind the scenes
- June 24, 29, July 6: Threads and Synchronization
- PDF slides
- Illustrates basics of getting threads to run:
- Illustrates threads corrupting data:
- Series of examples using an Account.
Some threads do deposits, some do withdraws on shared account.
- Two examples with multiple monitors
- Static methods have different monitors than instance methods:
- July 1: Class cancelled unexpectedly
- July 8 and 13: Networking
- July 15: Server-side Programming
- PDF slides
- JSDK 2.1 download for Windows (375K)
- Tim Downey's TomCat instructions
- This material is not in the text. Additional references:
- For all Java examples, save the HTML in main folder, place the
class files in your WEB-INF/servlets directory, and start the servletrunner.
The links will not run directly from my web page because
our web server is not running servlets.
- CGI program in C++ to print out what a form transmits.
prog1.html (uses POST), and
prog1b.html (uses GET).
- CGI script can be invoked from a Java program, so you cannot
assume the form has done verification:
- Findmax program using a servlet:
- Program to render PDF files (assumes get, so include
name of file, minus .pdf extension after a ? in the URL):
- Cookie example from slides:
- Session example from slides:
- July 22: Exam #2: Reflection, Java 1.5, Threading, Networking
- July 20 and 27: Serialization
- July 29 and August 3: Garbage Collection
- Java Developer Connection Article
shows that soft references don't stay around for a long time.
shows a factory class that hands out Foo objects
(from a pre-allocated pool),
but requires that the client release the objects back to the pool.
shows a factory class that hands out Foo objects,
but does not require that the client release the objects.
Instead it uses weak references to detect orphaned Foo objects,
and reclaims those orphans for the pool.
- August 5: Java 1.5
- August 10: Review of Java Material
- August 12: Exam #3