David Clarke, John Potter, and James Noble. Ownership types for flexible aliasing protection. In Proceedings of OOPSLA'98, ACM Press, 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
The Fox - A Tool for Java Object Graph Analysis - Potanin Self-citation (Noble) (Correct)
....ownership is that no object outside the owner b is allowed to have a reference to a. Ownership allows us to structure an object graph into an implicit ownership tree. Object ownership is in essence a generalisation of uniqueness [20] that underlies many more sophisticated alias management schemes [16, 20, 5]. To clarify this concept, consider an example in figures 2.5, 2.6, and 2.7. The first one gives a simple example of a memory graph with root R. The second one shows an ownership tree constructed from the graph just before, note how it has exactly the same number of nodes but a lot fewer edges. ....
....however, enough aliased objects that uniqueness alone will be insu#cient for managing aliasing within an object oriented programming style. 6.4. 2 Object Ownership Object ownership is in essence a generalisation of uniqueness [20] that underlies many more sophisticated alias management schemes [17, 5, 4, 16]. An object a owns another object b if all the paths from the root r to the object b go through a. In this case b is called the owner of a. The implication of ownership is that no object outside the owner b is allowed to have a reference to a. We posit a global root r through which all the objects ....
David Clarke, John Potter, and James Noble. Ownership types for flexible aliasing protection. In Proceedings of OOPSLA'98, ACM Press, 1998.
The Ins and Outs of Objects - Potter, Noble, Clarke (1998) (9 citations) Self-citation (Clarke Potter Noble) (Correct)
....a foundation for more sophisticated formal models for component based software development. In Section 2, we show that there is a natural way to group objects based on separability and reachability properties for an arbitrary object graph. Some of our earlier work dealing with object aliasing [12] discussed so called articulation point properties for object graphs. Articulation points provide single point cutsets for separating otherwise connected components of a graph [1] Articulation points play a crucial role in this paper: they provide a natural hierarchical structure for otherwise ....
....in some way. In Section 4 we consider the effect of changes to the object graph on ownership. We provide a constraint on changes that is sufficient to keep the ownership of existing objects invariant. Naively one might expect such a constraint to be enforceable only at run time. Elsewhere [30, 12, 33] we have reported on our approach to flexible alias protection where we annotate program texts with object contexts and ownership types. These annotations provide statically checkable constraints on the object graph structure. The static ownership types correspond to a run time ownership structure ....
[Article contains additional citation context not shown here]
D. Clarke, J. Potter, and J. Noble. Ownership types for flexible aliasing protection. In OOPSLA'98 Proceedings, 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC