QuoteRef: taivA9_1996

topics > all references > ThesaHelp: references t-z

references t-z
ACM references m-z
problems with type inheritance
incremental development
type inheritance as reuse
restricted and extended types
object-oriented programming
type inheritance
abstraction in programming language
object-oriented design
collection class
early vs. late binding
reusable programming
abstraction in programming
primitive data type as memory
inheritance of properties
inheritance by delegation
object-oriented prototypes
modes in a user interface
structural equivalence vs. name equivalence of data types
interface type
object-oriented procedures
parameter passing by message
abstract data type


Taivalsaari, A., "On the notion of inheritance", ACM Computing Surveys, 28, 3, pp. 438-479, September 1996. Google

abstract ;;Quote: although inheritance is central to object-oriented programming, researchers rarely agree on its meaning and usage
439 ;;Quote: inheritance allows the creation of a new class from existing classes; i.e., incremental program development
440 ;;Quote: inheritance is record combination; the record for a new class is like its parent's record, but extended with new properties
441 ;;Quote: object-oriented programming originated from Simula for modeling the concepts of an application domain
441+;;Quote: inheritance represents conceptual specialization of a model
441 ;;Quote: object-oriented programming directly supports abstraction by classification/instantiation, aggregation/decomposition, generalization/specialization, grouping/individualization
442 ;;Quote: object-oriented languages support aggregation/decomposition by using an object as a variable of another object
442 ;;Quote: object-oriented programming supports grouping/individualization by defining arbitrary collection classes such as lists and dictionaries
447 ;;Quote: the use of inheritance for conceptual specialization is rarely realized
452 ;;Quote: without late binding, newly defined components may not work with inherited operations; needed for incremental development
455 ;;Quote: inheritance with late binding, self-reference, and super-reference allows objects to be reused without textual copying or editing; a new way to write programs
455+;;Quote: late binding and self-reference allow a programmer to change object behavior without access to its representation
455+;;Quote: super-reference allows access to redefined properties without code duplication
459 ;;Quote: within computer memory, only reference and contiguity can express direct relationships
459 ;;Quote: implement inheritance by delegation or by concatenation; i.e., use reference to share an interface, or use contiguity to copy an interface
461 ;;Quote: inheritance by delegation allows changes to a parent node to automatically apply to descendants
466 ;;Quote: modify the behavior of an object with traits, dynamic inheritance, or modes; e.g., distinguish open and iconified windows
468 ;;Quote: selective inheritance blurs the distinction between parents and methods; i.e., a descendant can use a subset of a parent's identifiers as its own
469 ;;Quote: a mixin class implements properties solely for use in other classes; create a new class by combining mixins
471 ;;Quote: inheritance is synonymous with receiving; the parent and descendent share something with each other
741 ;;Quote: in object-oriented programs, inheritance means that the same compiled code is shared by descendents
472 ;;Quote: inheritance of state allows a parent to share or duplicate its variables with its descendents
472+;;Quote: in class-based systems, a class inherits the structure of the parent but not its contents or state
472 ;;Quote: most object-oriented systems use single dispatching; i.e., a message is sent to one object; e.g., "5+4" is
472+;;Quote: single dispatching does not match binary operations; e.g., possible code duplication for mixed integer and floating point arithmetic
473 ;;Quote: single dispatching encourages the definition of abstract data types; multiple dispatching does not
474 ;;Quote: object-oriented inheritance allows the extension and refinement of existing code without modifying the code. This is the essence of inheritance

Related Topics up

ThesaHelp: references t-z (309 items)
ThesaHelp: ACM references m-z (280 items)
Topic: problems with type inheritance (20 items)
Topic: incremental development (74 items)
Topic: type inheritance as reuse (27 items)
Topic: restricted and extended types (34 items)
Group: object-oriented programming   (26 topics, 814 quotes)
Group: type inheritance   (13 topics, 391 quotes)
Topic: abstraction in programming language (47 items)
Topic: object-oriented design (29 items)
Topic: collection class (11 items)
Topic: early vs. late binding (15 items)
Topic: reusable programming (77 items)
Topic: abstraction in programming (67 items)
Topic: primitive data type as memory (29 items)
Topic: inheritance of properties (24 items)
Topic: inheritance by delegation (8 items)
Topic: object-oriented prototypes (39 items)
Topic: modes in a user interface (40 items)
Topic: structural equivalence vs. name equivalence of data types (30 items)
Topic: interface type (50 items)
Topic: object-oriented procedures (41 items)
Topic: parameter passing by message (31 items)
Topic: abstract data type (64 items)

Collected barberCB 1/97
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.