[ajug-members] thinking about how to think
Dale at Newfield.org
Tue Sep 9 10:42:20 EDT 2008
Wilson, Jeff wrote:
> The way to think about OO is that there are a bunch of objects that
> describe the system, and work gets done by passing messages around
> between them.
You describe an "Object Based" system, not necessarily an "Object
Oriented" one. The latter assumes an object type system (so there's
more of a chance of having more than one of any given object in the
system) which typically includes some sort of inheritance mechanism
tying some of the types to one another (which typically allows for code
re-use given carefully enough thought out class hierarchies, and
additional polymorphism building upon those common super-classes).
More information about the ajug-members