Sciweavers

Free Online Productivity Tools i2Speak i2Symbol i2OCR iTex2Img iWeb2Print iWeb2Shot i2Type iPdf2Split iPdf2Merge i2Bopomofo i2Arabic i2Style i2Image i2PDF iLatex2Rtf Sci2ools

7

CONCURRENCY
2004

favoriteEmaildiscussreport

124views more CONCURRENCY 2004»

Checking ownership and confinement

13 years 4 months ago

Checking ownership and confinement

Download www.cs.ru.nl

Abstract. A number of formal proposals to manage aliasing in Java-like programming languages have been advanced over the last five years. Unfortunately, it is not clear how practical these proposals are, that is, how well they relate to the kinds of programs currently written in those languages. We have analysed heap dumps from a corpus of Java programs to identify their implicit aliasing structures, including object ownership, confinement, and uniqueness. Understanding the kinds of aliasing present in programs should help us to design formalisms to make explicit the kinds of aliasing implicit in object-oriented programs.

Alex Potanin, James Noble, Robert Biddle

Real-time Traffic

Aliasing | CONCURRENCY 2004 | Formal Proposals | Java-like Programming Languages |

claim paper

Related Content

» Featherweight generic confinement

» Inference and Checking of Object Ownership

» Ownership Confinement Ensures Representation Independence for ObjectOriented Programs

» Validity Invariants and Effects

» TypeBased Object Immutability with Flexible Initialization

» Confinement of matroid representations to subsets of partial fields

» Dynamically Checking Ownership Policies in Concurrent CC Programs

» Modular Safety Checking for FineGrained Concurrency

» Ownership types for safe regionbased memory management in realtime Java

Post Info
More Details (n/a)

Added	17 Dec 2010
Updated	17 Dec 2010
Type	Journal
Year	2004
Where	CONCURRENCY
Authors	Alex Potanin, James Noble, Robert Biddle

Comments (0)