Group:
memory management
Topic:
debugging by usage rules
Topic:
initialized constants
Topic:
read-only and write-once file systems
Topic:
safe use of pointers
Topic:
shared objects
Topic:
static single assignment; SSA
Topic:
unique names
| |
Subtopic: owned objects 
| Quote: Guava monitors are always synchronized; other instances are uniquely owned by a single monitor and never need synchronizing [»bacoDF10_2000]
| | Quote: an unshared Guava object is permanently owned by a shared monitor or unshared value; no other references [»bacoDF10_2000]
| | Quote: use single-bit reference count for owned objects; e.g., most list cells in Lisp [»abduSE9_1998]
| | 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 [»boylJ7_2005]
|
Subtopic: ownership for memory deallocation
| Quote: without garbage collection, objects must be owned; who releases a string that is queued for printing? [»swinDC7_1985]
| | Quote: memory leak detector based on owning pointers; automatically inferred; a class member always or never owns its pointee at public method boundaries; found errors in binutils and apache [»heinDL6_2003]
| | Quote: associate capability and type with each object; guarantees exclusive ownership for deallocation or reuse; extends linear type systems [»walkD7_2000]
|
Subtopic: resource leakage
| Quote: eliminate spurious paths in a Boolean program by automatically adding boolean control variables; e.g., resource allocation within loops and conditionals [»laruJR5_2004]
| | Quote: PREfix for path-by-path analysis across function boundaries; finds null pointers, improper memory allocation/deallocation; uninitialized variables, resource state errors, improper library usage [»laruJR5_2004]
| | Quote: Slam found many errors in Windows device drivers; it separates the control path from the data path; e.g., resource use [»laruJR5_2004]
|
Subtopic: immutable object
| Quote: Modeler uses immutable objects with unique names; allows name to be used in place of text [»lampBW6_1983]
|
Subtopic: tracking non-alias
| Quote: track non-aliasing of memory regions via tagged capabilities and type system [»walkD7_2000]
|
Related Topics
Group: memory management (11 topics, 367 quotes)
Topic: debugging by usage rules (41 items)
Topic: initialized constants (12 items)
Topic: read-only and write-once file systems (8 items)
Topic: safe use of pointers (102 items)
Topic: shared objects (13 items)
Topic: static single assignment; SSA (19 items)
Topic: unique names
(58 items)
|
