| 
|
QuoteRef: taivA11_1997
topics >
all references >
ThesaHelp:
references t-z
Topic:
software models of reality
Topic:
object-oriented design
Topic:
pseudocode design
Topic:
object-oriented classes
Topic:
classification
Group:
type inheritance
Topic:
object-oriented prototypes
Topic:
type hierarchy
Topic:
meaning by language as a whole
Reference
Taivalsaari, A., "Objects versus prototypes: Some philosophical and historical observations", JOOP, November/December 1997, pp. 44-50. Google
Notes
ftp://cs.uta.fi/pub/kevo
47 ;;Quote: the limited modeling of object-oriented programming suffices for most applications; typically shared properties; better than other paradigms
47 ;;Quote: use a consensus-driven process to design a vocabulary and a good enough class hierarchy; no optimum classification
47 ;;Quote: basic classes occur in the middle of the class hierarchy but object-oriented class design proceeds from top to bottom
47+;;Quote: need experience on the problem domain before designing the generic, more abstract classes
48 ;;Quote: Kevo uses family resemblance instead of explicitly sharing object representations
48+;;Quote: Kevo creates objects by copying; it incrementally modifies objects with operations over modules
49 ;;Quote: Kevo objects are in the same family if they share the same external interface; automatically maintained
ThesaHelp: references t-z (309 items)
Topic: software models of reality (22 items)
Topic: object-oriented design (29 items)
Topic: pseudocode design (43 items)
Topic: object-oriented classes (66 items)
Topic: classification (64 items)
Group: type inheritance (13 topics, 391 quotes)
Topic: object-oriented prototypes (39 items)
Topic: type hierarchy (18 items)
Topic: meaning by language as a whole (26 items)