| 
|
QuoteRef: alexRT1_2000
topics >
all references >
Topic:
access to components of a data object
Topic:
opaque and partially-opaque data types
Topic:
object-oriented packages
Topic:
initialization of data
Topic:
finalization of data
Topic:
type parameter
Topic:
separate a module's interface specification from its implementation
Topic:
persistent data structure
Topic:
dynamic type checking
Topic:
dynamic vs. static data type
Reference
Alexander, R.T., Bieman, J.M., Viega, J., "Coping with Java programming stress", Computer, January 2000, pp. 30-38. Google
30 ;;Quote: encapsulation should guard the integrity of the protected component or its owner
30 ;;Quote: Java protected access is an illusion; any class in the same package can modify it
32 ;;Quote: Java allows a superclass to call an overriding method before the object is initialized
33 ;;Quote: Java finalizers execute in an arbitrary order or not at all; avoid or use explicit garbage collection
34 ;;Quote: Java does not support specialized, homogeneous container classes
33 ;;Quote: a Java stack inherits its vector operations; it should hide the representation
35 ;;Quote: a final argument in Java does not prevent changes to the argument's object
35 ;;Quote: avoid Java initialization blocks; they can appear anywhere in a class; 'static' makes it a static initializer
36 ;;Quote: Java does not separate the public class interface from its implementation
37 ;;Quote: static type-checking may not catch type errors due to subclassing a function argument
Topic: access to components of a data object (4 items)
Topic: opaque and partially-opaque data types (14 items)
Topic: object-oriented packages (6 items)
Topic: initialization of data (42 items)
Topic: finalization of data (10 items)
Topic: type parameter (34 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: persistent data structure (37 items)
Topic: dynamic type checking (43 items)
Topic: dynamic vs. static data type (19 items)