Scribd
Upload
76 views

Lect01 PDF

Uploaded by

Suman Gopanola
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
76 views

Lect01 PDF

Uploaded by

Suman Gopanola
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

1: Introduction to Objects

The Progress of Abstraction


• Problem space & solution space
• Alan Kay’s 5 rules for a pure OOP
language
1) Everything is an object
2) A program is a bunch of objects telling
each other what to do by sending
messages
3) Each object has its own memory made up
of other objects
4) Every object has a type
5) All objects of a particular type can receive
the same messages

An Object has an interface


Type name Light
on()
off()
Interface brighten()
dim()
Characteristics + Behavior

Object Light lt = new Light();

Request lt.on();

That’s programming with objects!


3

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 1


The Hidden Implementation
• public, private, protected, and “friendly”

Class User
Class Creator (Client Programmer) 4

Reusing the Implementation


• Composition: make new objects by combining other
objects
Type name Car
start();
Interface drive();
etc...

Engine
Wheel[4]
Implementation
Door[2]
etc...

Inheritance: Reusing the interface


• Inheritance: Shape
automatically duplicates
the interface
draw()
• Objects related by erase()
inheritance all have the
same type (interface)

Circle Square Line


draw() draw() draw()
erase() erase() erase()

(This shows the UML style of drawing diagrams)

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 2


Polymorphism
One piece of code ...
... works with all these objects!

a Circle

draw()
Shape a Square
erase()

a Line

An Amazing Trick
void doStuff(Shape s) {
s.erase();
// ...
s.draw();
}

Circle c = new Circle();


Triangle t = new Triangle();
Line l = new Line();

doStuff(c); // "Dynamic binding"


doStuff(t);
doStuff(l);

Object-Oriented programs

object me
ss
ag
e
object
message
e
ag
ss
object me

• Made up of objects sending messages to each


other’s interfaces

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 3


OOP Design
• Most designs can be simplified by adding
another level of indirection/abstraction

Things Things
that that
Change Stay the
Same
• In the design
• At compile-time
• At run-time • Hard part: decomposing
• In the environment system into objects
• Etc. • What interfaces do you
need?
10

Object Landscapes & Lifetimes


• How are objects created and destroyed?
• Created in a pool of memory called the
heap
• Memory (only) is released by the garbage
collector
• Most flexible, simple way to build
a system
• Can also cost performance – but
not necessarily

11 11

Containers & Iterators


• You don’t know how many, what type,
lifetime of objects you need
• Where to put objects when you make them?
• Container:
generic holder
• Iterator: sequentially
selects items in the
container (called
Enumeration
in Java 1.0/1.1,
Iterator in Java 2)
12

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 4


Exception Handling for Errors

• Error handling
wired in
• Can’t ignore the error
• Recover to a known good state
• Java stands out: you’re forced to
use exceptions

13

Multithreading

• For responsiveness
• For running multiple tasks (animation &
networks)
• We’ll cover this in Chapter 14

14

Persistence
• Objects that live between program
invocations
• Convenient, Java has object serialization
built in, supports “lightweight
persistence.” Primarily added to support
remote method invocation (RMI) across
networks.
• JDBC could be thought of as
another form of persistence
• JavaSpaces, further
evolution
15

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 5


Java & the Internet
• A client-server system:
– Delivers centralized information on
demand
– Also accepts new information, typically
into a database (customer info, orders,
etc.)
• The web is a big client-server system
– All the servers are on the same network
– Client software is a universal “browser”
– Has been a dumb receiver of information
– Tedious & wastes bandwidth
16

Where Java Fits on the Web


• Designed to make interactive client programs, so the
Web server doesn’t have to do all the work
• Nicer UI, animation, data validation before sending it
across the web, provide local answers.
• Example: Plotting data
– Make a GIF on the server, send it on the net
– Send a few data points on the net, applet plots them
• The problem of client-side programming on the Web
• Java servlets, JSPs as the solution

17

Summary
Procedural Java
Abstract data type

Data Data
“Message”
Function Function Member
or
function
“Request”
Function or
Function
“method”

Function Function

“Encapsulation” (?) 18

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 6


Return to Home Page

Click Here
to Return to Home Page

19

Hands-on Java Seminar ©2000 Bruce Eckel http://www.BruceEckel.com page 7

You might also like