Algorithms and OOD (CSC 207 2013F) : Outlines
Held: Monday, 9 September 2013
Back to Outline 05 - Unit Testing.
On to Outline 07 - Arrays in Java.
We explore debugging, particularly the use of Eclipse's Java debugger.
- Some notes on Java.
- A bit about debugging.
- Reflection (maybe).
- New partners
- A friendly reminder that "Learning from Alumni" is a great opportunity
to get real-world recommendations on how to prepare for a job or
internship (and to network). And you get 1 credit. Thursdays, 2:15-4:05.
- I'm still working on getting HW1 graded. Time is just a limited commodity
(as I think you all know from your own experience).
- Note: Sometimes the html eboards don't get updated right after class.
You can always see what I typed by going to the original source.
- And send me a note if you see something missing.
- Reminder: Mentor session Wednesday night (8pm, I believe)
- Study break, tonight, 8pm, CS Commons
- Readings for Tuesday:
Making Your Own Classes and
Standard Object Methods.
- EC opportunities:
- Humanities Center Speaker Sarah Hendron, Wednesday, 7:30 p.m., JRC101
Waking the Machines: Art, Design, and Adaptive Technology
- Learning from Alumni 2:15-4:05 Thursday: Ian Lunderskov '08
- Tentative Thursday Extra: Matt Atherton '95
- CS Table, Friday: Trusting Trust.
Some Notes on Java
- As you've noted, it's relatively easy to call a
static method in
another class: you just write the name of the class, a period, and
the method name.
- Almost every method call will be preceded by something and a
period. Sometimes it's a class name (for static methods), sometimes
it's an object name (for object methods).
- I'm not going to do much about othe C-like aspects of Java. I assume
that you'll pick it up from examples, from searching, or from talking
Some Notes on Debuggers
- Amazingly, I don't have a lot to say about debuggers, other than that
I think they're a good idea, but not a silver bullet.
- Oh, I'll mention that I prefer textual debuggers like
- And we'll do a very quick demo.