| 
|
Topic: non-hierarchical classification and multiple classification
topics >
computer science >
decomposition of a system into levels
Topic:
hierarchical structures
Topic:
information retrieval by topic
Topic:
inheritance by delegation
Topic:
interface type
Topic:
limitations of hierarchical structures
Topic:
loosely structured data
Topic:
manual indexing
Topic:
multiple views for a user interface
Topic:
non-exclusive data type
Topic:
object-oriented classes
Topic:
object-oriented prototypes
Topic:
problem of assigning names
Topic:
problem of classifying information
Topic:
problems with type inheritance
Topic:
taxonomy
Topic:
type hierarchy
Group:
type inheritance
Topic:
using keywords to search hypertext
Topic:
weak vs. strong type checking
Summary
Information may be classified under multiple hierarchies and categorized into multiple folders or topics.Object-oriented classes may be constructed from multiple base classes and they may satisfy multiple interfaces. (cbb 11/07)
Subtopic: multiple inheritance
Quote: with interacting hierarchies, an explorer can specify multiple dimensions e.g., date and location [»shasD12_1987] Quote: can define multiple, overlapping hierarchies for information elements [»conkJ9_1987] Quote: in semantic nets, no predefined class hierarchy; every word is the root of its own hierarchy [»quilMR_1967]
Subtopic: inheritance vs. interfaces
Quote: need multiple inheritance for inheritance of interfaces and data layouts [»waldJ2_1992] Quote: Eiffel allows multiple inheritance; also used to combine abstract behavior (deferred class) with an implementation [»meyeB9_1990] Quote: an object or process instance may have more than one prototype description [»winoT7_1979] Quote: Pegasus types have unique names and represent collections of objects that share characteristics; interrelated by a DAG (multiple inheritance) [»ahmeR12_1991] Quote: in object-oriented programming, multiple inheritance is very useful; if not provided, it is approximated [»wolfW9_1989]
Subtopic: delegation
Quote: CLR uses single inheritance with multiple interfaces; all interface methods must be implemented [»hamiJ2_2003]
Subtopic: reuse requires frozen components
Quote: if want some object to share knowledge with a prototype, it delegates messages to the prototype that it can't handle [»liebH11_1986] Quote: an extension object uses delegation to forward a message to an appropriate receiver [»liebH11_1986] Quote: use delegation and prototypes to remove the distinction between class and instance [»liebH11_1986] Quote: it is easy to implement inheritance with delegation of messages, but not vice versa [»liebH11_1986]
Subtopic: parallel view
Quote: for software reuse must be able to freeze some elements of behavior while leaving others open; e.g., Eiffel's deferred classes [»meyeB9_1990]
Subtopic: problems with multiple inheritance
Quote: a Boxer port is a parallel view of another structure for non-hierarchical relationships [»diseAA9_1986]
Quote: multiple derivation is rejected for exceptions; ambiguous handlers; should handle both exceptions
[»buhrPA9_2000] .@#@
Topic: decomposition of a system into levels (49 items)
Topic: hierarchical structures (46 items)
Topic: information retrieval by topic (16 items)
Topic: inheritance by delegation (8 items)
Topic: interface type (50 items)
Topic: limitations of hierarchical structures (10 items)
Topic: loosely structured data (20 items)
Topic: manual indexing (19 items)
Topic: multiple views for a user interface (26 items)
Topic: non-exclusive data type (16 items)
Topic: object-oriented classes (67 items)
Topic: object-oriented prototypes (39 items)
Topic: problem of assigning names (25 items)
Topic: problem of classifying information (42 items)
Topic: problems with type inheritance (20 items)
Topic: taxonomy (16 items)
Topic: type hierarchy (18 items)
Group: type inheritance (13 topics, 394 quotes)
Topic: using keywords to search hypertext (26 items)
Topic: weak vs. strong type checking
(42 items)