@gron

Ownership Domains: Separating Aliasing Policy from Mechanism

, and . ECOOP 2004 – Object-Oriented Programming, volume 3086 of Lecture Notes in Computer Science, Springer, Berlin / Heidelberg, (2004)
DOI: 10.1007/978-3-540-24851-4_1

Abstract

Ownership types promise to provide a practical mechanism for enforcing stronger encapsulation by controlling aliasing in object-oriented languages. However, previous ownership type proposals have tied the aliasing policy of a system to the mechanism of ownership. As a result, these proposals are too weak to express many important aliasing constraints, yet also so restrictive that they prohibit many useful programming idioms. In this paper, we propose ownership domains , which decouple encapsulation policy from the mechanism of ownership in two key ways. First, developers can specify multiple ownership domains for each object, permitting a fine-grained control of aliasing compared to systems that provide only one ownership domain for each object. Second, developers can specify the permitted aliasing between each pair of domains in the system, providing more flexibility compared to systems that enforce a fixed policy for inter-domain aliasing. Because it decouples policy from mechanism, our alias control system is both more precise and more flexible than previous ownership type systems.

Description

Abstract - SpringerLink

Links and resources

Tags

community

  • @gron
  • @dblp
@gron's tags highlighted