Held: Wednesday, 22 January 2014

Back to Outline 02 - An Introduction to Java Development. On to Outline 04 - Unit Testing.

Summary

We begin our real exploration of Java by reading and correcting some code.

Related Pages

• Reading: Basics of Object-Oriented Problem Solving
• Reading: An Introduction to Java
• Reading: Simple Java for C Programmers
• Lab: Reading Java
• EBoard 3 (Source 3) (HTML 3) (PDF 3)

Overview

• Some notes on Java.
• Lab: Simple Code Reading (more or less).
• Reflection.

Administrivia

• Yes, we'll do attendance again today.
• Make sure to sign up for a fifteen-minute interview if you have not done so already.
• Please respond to Earnest's survey if you have not done so already.
• I got over 200 email messages from students on Tuesday.
  
  • (Yes, it's my fault for having students submit homework via email.)
  • So that I can navigate my inbox, It's very important to me that you take the time to title your email messages correctly.
• Just so you know, we're going to continue to learn how to use the lab equipment (so to speak) for the next few classes.
• Lab writeup: Extra 1.
  • Subject: CSC 207 Writeup 2: Reading Java (Your Name Here)
  • Due before class on Friday.
• Reading on Unit Testing for Friday's class.
• HW 2 distributed. Due next Wednesday at 10:30 p.m.
• I will hold a review session tomorrow at 10:00 a.m.
  (We probably don't need one yet, but I'd like to get started.)
• Extra credit: Thursday extra on summer research in CS, Thursday @ 4:30 in Noyce 3821.
• Extra credit: CS Table Friday at noon: 3D Printing (of body parts?).
• Extra credit: Theatre Gigante Friday evening.

A few more notes on Git

You may find it more convenient to use the following commit command, which doesn't open the editor.

git commit -m "*message*"

I'll admit that I prefer to open the editor and see a quick list of the changes I'm committing. (I also often write multi-line commit messages.)

Some notes on Java

• Yes, you'll find that Java looks a lot like C.
• Some big differences:
  • Everything goes in a class.
  • You have to indicate protection levels.
  • You have to give main parameters.
  • When you're treating Java like C, you need to put static before function (method) and global (field) declarations.
  • Java is much more sensitive about types.

Lab: Simple Code Reading

Do the lab on code reading and correction.

Reflection

What have you learned about Java?