 |
 |
Articles / TULARC / Software / OO Technology / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
3.1) What Is The "Classical" Object-Oriented Paradigm? |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Software / OO Technology / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
3.1) What Is The "Classical" Object-Oriented Paradigm? |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Object-Oriented Technology FAQ, by Bob Hathaway rjh@geodesic.com with numerous contributions by others.
This refers to the usual class and object model. Its any 2+ level system
as described in section 1.4. See also [Coplien 92].
Continue to:
programming, software, coding, Object-Oriented, language, dynamic binding, constructor, destructor, overriding, methods, inheritance, reflection, persistence, MFC, real-time, polymorphism, system, database, vendor
|
|
|
|
 |
|