Ownership Domains: Separating Aliasing Policy from Mechanism

Aldrich, Jonathan; Chambers, Craig

doi:10.1007/978-3-540-24851-4_1

Cited by 111 publications

(165 citation statements)

References 20 publications

Supporting

Mentioning

163

Contrasting

Order By: Relevance

“…The ownership type system of Lu et al [15] generalize this by using an additional accessibility modifier. Most closest to the ownership system presented in this paper is the general Ownership Domains [1] approach. The ownership system of this paper without traits together with an inference algorithm is presented in [19].…”

Section: Conclusion Related and Future Workmentioning

confidence: 99%

See 1 more Smart Citation

A Calculus for Boxes and Traits in a Java-Like Setting

Bettini

Damiani

Luca

et al. 2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The box model is a component model for the object-oriented paradigm, that defines components (the boxes) with clear encapsulation boundaries. Having well-defined boundaries is crucial in component-based software development, because it enables to argue about the interference and interaction between a component and its context. In general, boxes contain several objects and inner boxes, of which some are local to the box and cannot be accessed from other boxes and some can be accessible by other boxes. A trait is a set of methods divorced from any class hierarchy. Traits can be composed together to form classes or other traits. We present a calculus for boxes and traits. Traits are units of fine-grained reuse, whereas boxes can be seen as units of coarse-grained reuse. The calculus is equipped with an ownership type system and allows us to combine coarse-and fine-grained reuse of code by maintaining encapsulation of components.

show abstract

Section: Conclusion Related and Future Workmentioning

confidence: 99%

“…To guarantee encapsulation of certain objects of a box an ownership type system [8,6,15,9] is used. It defines two ownership domains [1,24,19] for each box, namely a local and a boundary domain. Each object of a box and each inner box is located in one of these domains.…”

Section: Introductionmentioning

confidence: 99%

A Calculus for Boxes and Traits in a Java-Like Setting

Bettini

Damiani

Luca

et al. 2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…In [14,2] objects on the stack are allowed to break deep ownership, and to refer to the inside of an ownership context. A more refined approach [1] decouples the encapsulation policy from the ownership mechanism, by allowing multiple ownership domains (contexts in our terminology) per object, and by allowing the programmer to specify permitted aliasing between pairs of contexts.…”

Section: Types For Hierarchic Shapesmentioning

confidence: 99%

Types for Hierarchic Shapes

Drossopoulou

Clarke

Noble

2006

Programming Languages and Systems

View full text Add to dashboard Cite

Abstract. Heap entities tend to contain complex references to each other. To manage this complexity, types which express shapes and hierarchies have been suggested. We survey type systems which describe such hierarchic shapes, how these types are used for reasoning about programs, and applications in concurrent programming.Most imperative programs create and manipulate heap entities (objects, or records) which contain references to each other forming intricate topologies. This creates complexity, and makes programs difficult to understand and manipulate. Programmers, on the other hand, tend to think in terms of shapes, categorizations and hierarchies.Thus, in the last decade, types describing shapes and hierarchies have been proposed to express programming intuitions, to support verification, and for synchronization and optimizations. We will discuss types for hierarchic shapes in terms of object oriented programming, because, even though the ideas are applicable to any imperative language, most of the related research was conducted in the context of object oriented languages.

show abstract

“…A heap effect is an assignment to some object fields. 2 The advice has no direct assignments to object fields, but we must also determine the potential side effects of the methods it calls. Methods like reset presumably have heap effects, and methods like getSpaceship presumably do not, though in practice we would need to verify that.…”

Section: A Tale Of Two Aspectsmentioning

confidence: 99%

“…Concern Domains. We use a shallow ownership type and effect system [2,5] to identify explicitly the concerns that own each object or aspect in the program. Programmers and tools can inspect the domain declarations and so statically determine how an aspect will interact with objects, or if two aspects may potentially interfere.…”

Section: Introductionmentioning

confidence: 99%

MAO: Ownership and Effects for More Effective Reasoning About Aspects

Clifton¹,

Leavens²,

Noble³

ECOOP 2007 – Object-Oriented Programming

View full text Add to dashboard Cite

Aspect-oriented advice increases the number of places one must consider during reasoning, since advice may affect all method calls and field accesses. MAO, a new variant of AspectJ, demonstrates how to simplify reasoning by allowing programmers, if they choose, to declare limits on the control and heap effects of advice. Heap effects, such as assignment to object fields, are specified using concern domains--declared partitions of the heap. By declaring the concern domains affected by methods and advice, programmers can separate objects owned by the base program and by various aspects. When desired, programmers can also use such concern domain annotations to check that advice cannot interfere with the base program or with other aspects. Besides allowing programmers to declare how concerns interact in a program, concern domains also support a simple kind of semantic pointcut. These features make reasoning about control and heap effects easier. KeywordsAspect-oriented programming, ownership, concern domain, control effects, heap effects, heap effect dependency, writes, curbing, spectator, AspectJ language, MAO language (1) Rose-Hulman Institute of Technology, Terre Haute, Indiana, USA (2) Iowa State University, Ames, Iowa, USA (3) Imperial College, London, UK (4) Permanent: Victoria University of Wellington, New Zealand Abstract. Aspect-oriented advice increases the number of places one must consider during reasoning, since advice may affect all method calls and field accesses. MAO, a new variant of AspectJ, demonstrates how to simplify reasoning by allowing programmers, if they choose, to declare limits on the control and heap effects of advice. Heap effects, such as assignment to object fields, are specified using concern domains-declared partitions of the heap. By declaring the concern domains affected by methods and advice, programmers can separate objects owned by the base program and by various aspects. When desired, programmers can also use such concern domain annotations to check that advice cannot interfere with the base program or with other aspects. Besides allowing programmers to declare how concerns interact in a program, concern domains also support a simple kind of semantic pointcut. These features make reasoning about control and heap effects easier.

show abstract

Ownership Domains: Separating Aliasing Policy from Mechanism

Cited by 111 publications

References 20 publications

A Calculus for Boxes and Traits in a Java-Like Setting

A Calculus for Boxes and Traits in a Java-Like Setting

Types for Hierarchic Shapes

MAO: Ownership and Effects for More Effective Reasoning About Aspects

Contact Info

Product

Resources

About