Sciweavers

OOPSLA
1995
Springer

How and Why to Encapsulate Class Trees

13 years 8 months ago
How and Why to Encapsulate Class Trees
eusable framework, pattern or module interface usually is represented by abstract They form an abstract design and leave the implementation to concrete subclasses. ract design is instantiated by naming these subclasses. Unfortunately, this exposes implementation details like class names and class tree structures. The paper gives a rationale and a general metaobject protocol design that encapsulates whole class trees. Clients of an abstract design retrieve classes and create objects based on class semantics specificasing abstract classes as the only interface enhances information hiding and makes it easier both to evolve a system and to configure system variants.
Dirk Riehle
Added 26 Aug 2010
Updated 26 Aug 2010
Type Conference
Year 1995
Where OOPSLA
Authors Dirk Riehle
Comments (0)