| 
|
QuoteRef: liskB_1996
topics >
all references >
ThesaHelp:
references i-l
ThesaHelp:
ACM references f-l
Topic:
localized understanding
Topic:
deployable module or assembly
Topic:
what is truth
Topic:
object and value equivalence
Topic:
separate a module's interface specification from its implementation
Topic:
program module as encapsulation
Topic:
dependency analysis
Topic:
information hiding
Group:
requirement specification
Topic:
importance of information hiding for requirement specification
Topic:
shared objects
Topic:
replacement as setting a reference to a value
Topic:
safe use of pointers
Topic:
immutable files and data
Topic:
integer values and operations
Topic:
arrays
Topic:
range checking
Topic:
data type as a set of operations
Topic:
type parameter
Topic:
object-oriented procedures
Topic:
notation for operations
Topic:
generic operations and polymorphism
Topic:
inheritance of properties
Topic:
abstract data type
Topic:
failure returning functions and expressions
Group:
exception handling
Reference
Liskov, B., "A history of CLU, with transcript of presentation", pp. 471-510, in Bergin, T.J., Jr., Gibson, R.G., Jr. (ed.), History of Programming Languages-II, New York, ACM Press, 1996. Google
475 ;;Quote: the goal is to implement and reason about each module separately
475+;;Quote: a module can replace another if it implements the same abstraction; without changing other modules
476 ;;Quote: independent modules require encapsulation and specification
476+;;Quote: if one module depends on the implementation details of another module, it may need changing when the other changes
476+;;Quote: if a module accesses another object's representation, independent replacement is impossible
476 ;;Quote: information hiding conflicts with code reading and other desirable activities
476+;;Quote: encapsulation reduces the need for information hiding
476 ;;Quote: a specification allows different implementations of a program module
476+;;Quote: a specification allows one to use a program module before it is defined
476+;;Quote: code is not a specification because it does not separate what is required from ways of achieving it
484 ;;Quote: in CLU, an assignment causes sharing; after 'x:=y' both x and y refer to the same object
484 ;;Quote: mutable objects may be shared as long as pointer manipulation is disallowed
484 ;;Quote: CLU stores small immutable objects in variables, e.g., integers and Booleans; programs can not detect the lack of sharing
485 ;;Quote: CLU arrays do not contain uninitialized elements; they grow and shrink on either end with bounds checking as needed
486 ;;Quote: CLU type-checks parameterized types via a 'where' clause that defines the required operations
487 ;;Quote: the name of a CLU operation is always 't$o' where 't' is a type name; avoids overloading and enhances program correctness and readability
492 ;;Quote: most object-oriented languages allow subclasses to use implementation details of a superclass; limited encapsulation
499 ;;Quote: Liskov got the idea for abstract data type in 1972; access the private data of an object via public operations; could be implemented in Simula 67
506 ;;Quote: in CLU, an exception is as efficient as a normal return; use exceptions to distinguish multiple returns
ThesaHelp: references i-l (342 items)
ThesaHelp: ACM references f-l (241 items)
Topic: localized understanding (43 items)
Topic: deployable module or assembly (10 items)
Topic: what is truth (66 items)
Topic: object and value equivalence (60 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: program module as encapsulation (28 items)
Topic: dependency analysis (31 items)
Topic: information hiding (50 items)
Group: requirement specification (11 topics, 306 quotes)
Topic: importance of information hiding for requirement specification (23 items)
Topic: shared objects (13 items)
Topic: replacement as setting a reference to a value (10 items)
Topic: safe use of pointers (102 items)
Topic: immutable files and data (57 items)
Topic: integer values and operations (13 items)
Topic: arrays (57 items)
Topic: range checking (20 items)
Topic: data type as a set of operations (38 items)
Topic: type parameter (34 items)
Topic: object-oriented procedures (41 items)
Topic: notation for operations (18 items)
Topic: generic operations and polymorphism (65 items)
Topic: inheritance of properties (24 items)
Topic: abstract data type (64 items)
Topic: failure returning functions and expressions (24 items)
Group: exception handling (12 topics, 305 quotes)