Encapsulation and Inheritance in Object-Oriented Programming Languages.

Snyder, A. (1986). Encapsulation and Inheritance in Object-Oriented Programming Languages. OOPSLA '86 Proceedings, 21(11), 38-45.

Type

Conference paper

Intellectual base

Primary research

Year

1986

Volume

21

Issue

11

Pages

38-45

DOI

10.1145/28697.28702

DOI registrant

Association for Computing Machinery

Link

https://doi.org/10.1145/28697.28702

Cited from

computer_science

Cited by

2 citations across 2 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Inheritance
  • A parent and a derivative. Two entities, one prior and one derived from it — superclass and subclass, ancestor and descendant, decedent and heir, species and subspecies. A directed lineage relation. An asymmetric "derives from" relation linking derivative to parent; it is distinct from copying (the parent persists) and from composition (parts independently chosen). Default carrying-over. By default the parent's structure, behaviour, or claims apply to the derivative without re-derivation — methods, alleles, estate, binding precedent transmitted for free. Selective override and extension. The derivative may specialise, override, or augment portions of what it received while remaining recognisably "of the parent" along the un-overridden portions; this override is what makes inheritance generative rather than mere copying. The substitutability invariant. Frequently the derivative can stand wherever the parent was expected (Liskov substitution, a subspecies counting as the species, a junior court speaking with its lineage's authority), constraining which overrides are admissible. The downward-coupling liability. Because children depend on inherited facts, a change to the parent can propagate to — and break — every derivative (the fragile-base-class problem, gene-network constraint, stare-decisis caution).

    This sourceIdentifies the tension between inheritance and encapsulation underlying the fragile-base-class problem.

Domain-specific

• Object-Oriented Programming
  • Snyder's analysis shows why encapsulation and inheritance are separable design dimensions rather than synonyms.

Verification

Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:9ef016fdcf32 · see in the full table