Object Ownership for Dynamic Alias Protection

Authors:
James Noble;David Clarke;John Potter
Affiliations:
-;-;-
Venue:
TOOLS '99 Proceedings of the 32nd International Conference on Technology of Object-Oriented Languages
Year:
1999

Citing 0
Cited 10

Simple Ownership Types for Object Containment

ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
ConstrainedJava

OOPSLA '04 Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Object-oriented encapsulation for dynamically typed languages

OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Dynamic ownership in a dynamic language

Proceedings of the 2007 symposium on Dynamic languages
Minimal Ownership for Active Objects

APLAS '08 Proceedings of the 6th Asian Symposium on Programming Languages and Systems
Unifying theories of locations

UTP'08 Proceedings of the 2nd international conference on Unifying theories of programming
Read-only execution for dynamic languages

TOOLS'10 Proceedings of the 48th international conference on Objects, models, components, patterns
Cloning in ownership

Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Ownership, filters and crossing handlers: flexible ownership in dynamic languages

Proceedings of the 8th symposium on Dynamic languages
Ownership types: a survey

Aliasing in Object-Oriented Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

Interobject references in object-oriented programs allow arbitrary aliases between objects. By breaching objects' encapsulation boundaries, these aliases can make programs hard to understand and especially hard to debug. We propose using an explicit, run-time notion of object ownership to control aliases between objects in dynamically typed languages. Dynamically checking object ownership as a program runs ensures the program maintains the encapsulation topology intended by the programmer.