| 
|
QuoteRef: boylJ7_2005
Topic:
immutable files and data
Topic:
owned resources and data objects
Topic:
separate a module's interface specification from its implementation
Reference
Boyland, J., "Why we should not add readolnly to Java (yet)", ECOOP 2005 Workshop on Formal Techniques for Java-like Programs, July 2005, http://www.cs.uwm.edu/~boyland/papers/readonly.pdf, pp. notes from preprint, pp.13. Google
6 ;;Quote: read-only does not fully express the idea of an array that is owned by a unique pointer, an immutable array, or an array for copying only
8 ;;Quote: disallow observational exposure of a read-only representation; makes the representation part of the abstract interface and allows concurrency errors
Topic: immutable files and data (59 items)
Topic: owned resources and data objects (12 items)
Topic: separate a module's interface specification from its implementation (86 items)