The Geneva convention on the treatment of object aliasing

Hogg, John; Lea, Doug; Wills, Alan; deChampeaux, Dennis; Holt, R.M.

doi:10.1145/130943.130947

Cited by 127 publications

(54 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our work belongs to the category of mechanisms for alias prevention [21] in general, and uses the ownership types idea in particular.…”

Section: Discussion and Related Workmentioning

confidence: 99%

A Parameterized Type System for Simple Loose Ownership Domains.

Schaefer¹,

Poetzsch-Heffter²

2007

JOT

View full text Add to dashboard Cite

Ownership Domains generalize ownership types. They support programming patterns such as iterators that are not possible with ordinary ownership types. However, they are still too restrictive for cases in which an object X wants to access the public domains of an arbitrary number of other objects, which often happens in observer scenarios. To overcome this restriction, we develop so-called loose domains which abstract over several precise domains. Similar to the relation between supertypes and subtypes, we get a relation between loose and precise domains. In addition, we simplify ownership domains by reducing the number of domains per object to two and hard-wiring the access permissions between domains. We formalize the resulting type system for an OO core language and prove type soundness and a fundamental accessibility property.

show abstract

“…Our work belongs to the category of mechanisms for alias prevention [21] in general, and uses the ownership types idea in particular.…”

Section: Discussion and Related Workmentioning

confidence: 99%

A Parameterized Type System for Simple Loose Ownership Domains.

Schaefer¹,

Poetzsch-Heffter²

2007

JOT

View full text Add to dashboard Cite

show abstract

“…However, it is not fine-grained enough to address the encapsulation problems related to object aliasing [18]. Reasoning about a class in an object-oriented program involves reasoning about the behavior of its instances, and those instances will depend for their correct operation on subobjects instantiated from other classes.…”

Section: The Problem Of Fragile Data Structuresmentioning

confidence: 99%

Object-oriented encapsulation for dynamically typed languages

Schärli

Black

Ducasse

2004

Proceedings of the 19th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

View full text Add to dashboard Cite

Encapsulation in object-oriented languages has traditionally been based on static type systems. As a consequence, dynamically-typed languages have only limited support for encapsulation. This is surprising, considering that encapsulation is one of the most fundamental and important concepts behind object-oriented programming and that it is essential for writing programs that are maintainable and reliable, and that remain robust as they evolve.In this paper we describe the problems that are caused by insufficient encapsulation mechanisms and then present object-oriented encapsulation, a simple and uniform approach that solves these problems by bringing state of the art encapsulation features to dynamically typed languages. We provide a detailed discussion of our design rationales and compare them and their consequences to the encapsulation approaches used for statically typed languages. We also describe an implementation of object-oriented encapsulation in Smalltalk. Benchmarks show that extensive use of objectoriented encapsulation results in a slowdown of less than 15 per cent.

show abstract

“…The goal of the type system is to provide alias control and invariance of aliasing properties, like role separation, restricted visibility etc. [12].…”

Section: Conclusion Future and Related Workmentioning

confidence: 99%

A Type System for Components

Dardha

Giachino

Lienhardt

2013

Software Engineering and Formal Methods

View full text Add to dashboard Cite

Abstract. In modern distributed systems, dynamic reconfiguration, i.e., changing at runtime the communication pattern of a program, is challenging. Generally, it is difficult to guarantee that such modifications will not disrupt ongoing computations. In a previous paper, a solution to this problem was proposed by extending the object-oriented language ABS with a component model allowing the programmer to: i) perform updates on objects by means of communication ports and their rebinding; and ii) precisely specify when such updates can safely occur in an object by means of critical sections. However, improper rebind operations could still occur and lead to runtime errors. The present paper introduces a type system for this component model that extends the ABS type system with the notion of ports and a precise analysis that statically enforces that no object will attempt illegal rebinding.

show abstract

The Geneva convention on the treatment of object aliasing

Cited by 127 publications

References 9 publications

A Parameterized Type System for Simple Loose Ownership Domains.

A Parameterized Type System for Simple Loose Ownership Domains.

Object-oriented encapsulation for dynamically typed languages

A Type System for Components

Contact Info

Product

Resources

About